PegBit Core — the production layer for enterprise AI.
From pilot to production, inside your boundary. Evaluation, guardrails, audit trails and vendor-neutral model routing — designed to run inside your own boundary, so your data never has to leave it.
Formerly called Omos.
The production layer already runs inside our own products. PegBit Core is what we’re extracting from it.
PegBit Core is designed to deploy inside your own cloud or tenancy, so sensitive data never crosses the boundary that owns it. The reason teams build in-house becomes the reason they choose Core.
Evaluation, guardrails, audit trails, monitoring and cost control are the product's core — not enterprise add-ons. The hard 20% that sinks DIY builds ships in the box.
Vendor-neutral model routing with automatic failover across providers. Models change monthly; your system shouldn't have to. Core is the stable layer over an unstable model market.
Give your team an AI that knows every policy, playbook and process you’ve written. Grounded in your own knowledge, citing every source, with a full audit trail.
In build The engine runs in production today; the Deploy workspace is being built now.
Ship AI features to your users without building the plumbing: API and SDK integration, an adapter per domain, isolation enforced per product. Shown as “Powered by PegBit Core” by default, or under your own brand at the Enterprise tier.
Live The same patterns run inside Sydence and AI Kraft today.
- The Reading RoomLiveIt learns your product
Feeds on your product's documents, workflows and data — and only yours — so it understands your world, not the internet's.
- The BrainLiveIt answers, honestly
Replies in plain language, grounded only in what your product actually knows, and cites its source. If it doesn't know, it says so.
- Quality DeptIn buildIt keeps knowledge healthy
Watches for gaps and contradictions in the background. The foundation runs today; the live health score is being built.
- Translation BureauIn buildIt speaks your languages
English natively today, with Yoruba and Hausa next, then Igbo, Swahili, Zulu and Twi. Native reasoning, not translated English.
- The VaultLiveIt remembers, defensibly
Every action is logged today. We're building toward a permanent, tamper-proof record of every answer too.
- The HandsLiveIt acts, not just answers
Creates tasks, updates records, drafts documents — validated at every step, reversible where it can be, and fully audited.
- The WatchtowerIn buildIt watches while you work
Daily digests, alerts on blockers and deadlines, and anomaly detection, so answers arrive before people think to ask.
- The SwitchboardLiveIt routes without lock-in
Every request goes to the best-fit model, with automatic failover across providers. One lab's bad day doesn't take you down.
- The GatekeeperIn buildIt refuses what it should
Input sanitisation, prompt-injection defence, PII redaction and action re-validation — trust as architecture a procurement team can approve.
- The RegistrarRoadmapIt respects your rules
Retention windows, legal holds, data-subject requests and audit exports — designed to align with NDPR, GDPR and SOC 2.
Like a credit score for your product’s knowledge — and it shows exactly what’s dragging the score down and how to raise it. The signals are already tracked inside the engine; the score itself is being built now.
- Coverage — how much of what your team asks it can answer
- Consistency — contradictions across your knowledge
- Freshness — how up to date your knowledge is
- Depth — how thoroughly each topic is covered
- Accessibility — availability in your team's languages
The developer experience we’re building toward. The engine already runs inside our own products; the self-serve SDK and adapters are next on the roadmap.
- 1. Connect your product — through the SDK.
- 2. Configure your adapter — what it knows, what it can do, how it speaks.
- 3. Go live — answering, acting and monitoring inside your product.
// Illustrative — not yet public
import Core from '@pegbit/core'
const client = new Core({
apiKey: process.env.PEGBIT_CORE_KEY,
product: 'your-product-id'
})Illustrative only. The SDK is not yet public.
- — Intelligence patterns live inside Sydence and AI Kraft
- — ExamSurf running on the same core
- — Extracting the shared patterns into PegBit Core
- — Opening the first design-partner slots
- — Self-serve SDK & integration API
- — Adapter framework per domain
- — Design partners live in production
- — Public availability & pricing
- — Enterprise deployment & compliance
- — Marketplace of domain adapters
We’re looking for a small handful of design partners to shape the platform before it goes wide. Not beta testers — strategic collaborators with real influence on what gets built. Two or three slots per door.
- — A real business, real users, and a problem Core could solve
- — A weekly conversation with our founder and engineers
- — Honest feedback, on time, on the record
- — Willingness to be a public case study at launch
- — 6–12 months on generous terms (free or heavily discounted)
- — A direct line to the founder and engineering
- — Real influence on the roadmap
- — Founding-partner recognition when we go public
Data isolation, model neutrality, grounding and the audit trail are live today; guardrails, deployment options and compliance controls are labelled honestly as in build or roadmap. Read the full security model →
Tell us about your organisation or product, and which door fits.