AI that can't lie,
leak, or go rogue
O-Lang is a governed workflow language with its own runtime, tool registry, and cryptographic audit layer. Write AI workflows that can't lie, leak data, or exceed their declared scope — from first line to production.
Already using LangChain, CrewAI, or OpenAI Agents? O-Lang governs their tool calls without replacing them.
// O-Lang — Bank Balance Workflow Workflow "Bank Balance Check" with user_question, customer_id Allow resolvers: - @o-lang/bank-account-lookup - @o-lang/llm-groq Step 1: Ask @o-lang/bank-account-lookup "{customer_id}" Save as account_info Step 2: Ask @o-lang/llm-groq "{user_question}. Balance is {account_info.balance}." Save as response Return response
Where O-Lang Works
Today
Governed AI workflows for critical domains. Start with our fastest deployment option, or explore deeper integrations.
Financial Services
Safe customer assistants that answer balance questions, explain policies, and block unauthorized transfers — in English, Yoruba, Swahili, Zulu & more.
Example
User: "What's my balance for CUST-001?"
Bot: "Your balance is ₦12,450. For transactions, use your app."
User: "Fi 5000 naira ranṣẹ..."
Bot: "⚠️ Transfers blocked. Visit a branch."
Healthcare & ICU
Patient admission workflows that enforce team scopes, prevent unauthorized actions, and log every decision cryptographically for compliance.
Workflow
- • Verify team authorization for ward access
- • Check bed availability in real-time
- • Summarize admission for clinical handoff
- • Block treatment suggestions outside scope
Government & IoT
Audit-ready workflows for public services: permit approvals, sensor data validation, and citizen queries — with cryptographic proof of every action.
Use Case
- • Validate citizen ID before service access
- • Cross-reference sensor data with policy rules
- • Generate tamper-evident audit logs
- • Escalate exceptions to human reviewers
Start in 60 seconds: Add a governed chatbot to any website. No code required.
💬 Deploy Chatbot WidgetWorks on WordPress, React, static HTML — or integrate deeper via our SDK.
Workflow domains in v1.1
Cryptographic audit coverage
Hallucinations in governed scope
Open source license
Write it once.
The kernel enforces it forever.
Declare your workflow in O-Lang. The kernel enforces every tool call, intent boundary, and safety constraint at runtime — deterministically, with a cryptographic receipt. No framework needed.
Wrap your existing tools
Write a .ol file. Declare your inputs, the tools it may call, and the intent scope. The kernel reads this as the authoritative contract — nothing outside it runs.
Kernel intercepts every call
The kernel sits between your orchestration layer and your tools. Every call is validated against the allowlist, intent-checked, and safety-filtered — before it reaches the tool. Your framework never knows.
Cryptographic audit trail
Every execution is SHA3-256 fingerprinted and ED25519-signed by the kernel. Your outputs are verifiable, tamper-evident, and ready for compliance.
Everything a governed
AI runtime needs
Tool Allowlists
Every workflow declares exactly which tools it may call. Any unlisted tool is rejected by the kernel at runtime — no exceptions.
@governance.allowed_toolsVerified Intent
Declare scope and prohibited actions. The kernel enforces both before and after execution — zero tolerance for scope creep.
__verified_intentCryptographic Audit
Every execution produces a SHA3-256 fingerprint, chained to the previous, and signed with ED25519. Full deterministic proof.
sha3-256 · ed25519Symbol Resolution
Steps compose with typed symbols. Each tool declares its output schema — downstream steps receive validated, typed data, never raw LLM output.
$step.symbol.fieldPII Detection & Safety
The kernel detects and redacts PII automatically on every execution — no extra tool needed. Covers 20+ languages including Yoruba, Igbo, Hausa, Swahili, and Zulu. Hallucinations and prompt injection blocked at the same layer.
kernel-native · 20+ languagesTool Registry
Publish, version, and discover tools at olang.cloud/registry. Every tool is signed and schema-validated before listing.
@o-lang/tool-nameGovernance that speaks
your language
O-Lang's kernel detects and redacts PII automatically on every execution — in 20+ languages, with first-class support for African languages that every major AI framework ignores. No extra configuration. No optional plugin.
African Languages
First-class support — not an afterthought
Yoruba
West Africa
Igbo
West Africa
Hausa
West Africa
Swahili
East Africa
Zulu
Southern Africa
Xhosa
Southern Africa
Amharic
East Africa
Somali
East Africa
Detects names, phone numbers, national IDs, addresses, and financial identifiers written natively in each language — not transliterated, not approximated.
Also supported
workflow · kernel auto-redacts PII
Workflow "Customer Support" with message, lang
// No PII resolver needed — kernel handles it// automatically for all 20+ supported languages
Allow resolvers:- @o-lang/llm-groq
Constraint: lang in ["yo", "ha", "sw", "ig", "en"]
Step 1: Ask @o-lang/llm-groq "{message}" ↑ kernel redacted PII before this ranSave as response
Return response20+
Languages supported
including 8 African languages
8
African languages — live
Yoruba, Igbo, Hausa, Swahili, Zulu, Xhosa, Amharic, Somali
1.4B+
People represented
across supported African languages
Write and run
.ol files in your
browser
No install. No config. Connect to the O-Lang cloud kernel and execute governed workflows live.
- Monaco editor with O-Lang syntax highlighting
- Real-time execution trace — see every resolver step
- Live safety logs and cryptographic audit output
- Save and share workflows with a permanent URL
// ICU Admission — Healthcare workflow workflow icu_admission_v1 { @governance { allowed_resolvers: [ "@o-lang/icu-admission", "@o-lang/llm-groq" ] scope: "team-a-icu-only" prohibited_actions: [ "unauthorized_procedure", "ward_transfer_without_auth" ] } step admit = @o-lang/icu-admission({ patient_id: $input.patient_id, ward: $input.ward, team: $input.team }) }
Every tool is signed,
versioned, and governed
O-Lang has its own tool ecosystem. Each tool (called a resolver internally) is a versioned, schema-validated package published to the O-Lang registry — not a wrapper around someone else's SDK.
o-lang kernel — your execution layer
underlying APIs (tools call these)
your tools — completely unchanged
Your frameworks call tools. O-Lang intercepts those calls, enforces governance, and returns signed output. Nothing in your existing stack changes.
@o-lang/llm-groq
Governed LLM calls with intent enforcement and output validation
@o-lang/bank-account-lookup
Read-only financial data tool with audit-signed output
@o-lang/icu-admission
Clinical workflow tool with team-scope enforcement
@o-lang/semantic-search
Vector retrieval with schema-validated, typed output
@o-lang/legal-extractor
Contract clause extraction with prohibition enforcement
your-tool
Publish any tool to the registry — HTTP, any language
JSON in, JSON out. That's the whole contract.
If your tool speaks JSON, O-Lang can govern it. Python, Go, Rust, Java, Bash, WASM — the kernel is indifferent to language. It only cares about the shape of the data, not who produced it.
Discover and publish
governed tools
Every tool in the registry is schema-validated, version-pinned, and signed. Drop it into any workflow with a single import.
@o-lang/bank-account-lookup
Secure account balance and transaction lookup with PII validation and multi-jurisdiction audit compliance.
@o-lang/icu-admission
ICU bed management, team-scoped admission, and HIPAA-compliant patient data handling.
@o-lang/llm-groq
Fast, governed LLM inference via Groq. Output schema-validated and hallucination-filtered.
@o-lang/notify-telegram
Send governed notifications to Telegram channels or users. Rate-limited, audit-logged, and allowlist-enforced.
@o-lang/semantic-doc-search
Vector-based semantic document search with scoped retrieval. Prevents out-of-context document access.
@o-lang/js-olang-tester
Unit and integration test harness for O-Lang workflows. Simulates resolver chains and validates governance policy enforcement.
@o-lang/python-olang-tester
Python test harness for O-Lang workflows. Available on PyPI. Validates resolver behaviour and policy compliance from Python environments.
@o-lang/legal-extract
Extract-only legal document analysis. Blocks legal advice output under GDPR, UK Companies Act, US Federal, and other jurisdictions.
@o-lang/llm-openai
OpenAI GPT-4o resolver with output schema enforcement and rate-limit-aware execution.
@o-lang/pii-validator
Global PII validation across 40+ identity formats: SSN, NIN, BVN, NHI, TFN, Aadhaar, and more.
@o-lang/device-commander
Govern device command dispatch to IoT endpoints — validates command signatures, enforces actuation allowlists, and logs every instruction to the audit chain.
@o-lang/sensor-router
Route sensor data events through governed alert pipelines — threshold checking, anomaly detection, and conditional escalation with full traceability.
@o-lang/infra-monitor
Infrastructure health monitoring — aggregates uptime, latency, and error rate signals into governed status reports with SLA enforcement.
Governed AI for
high-stakes domains
O-Lang was designed for industries where AI errors are not just inconvenient — they are dangerous, illegal, or catastrophic. Finance. Healthcare. Government. IoT.
Finance
Balance inquiries, transaction classification, fraud detection — with multilingual PII redaction (including Yoruba, Hausa, Swahili), hallucination prevention, and audit-ready compliance trails.
Healthcare
ICU admissions, clinical triage, ward management — with team-scoped access, HIPAA filters, and zero-tolerance prohibited procedure enforcement.
Legal
Contract extraction, NDA review, clause identification — extract-only mode blocks legal advice output, protecting against unauthorized practice of law.
IoT & Infrastructure
Device command governance, sensor data pipelines, automated alert routing — with strict tool allowlists preventing unauthorised actuation and real-time audit trails for every device action.
Everything you need
to build governed AI
From installing the kernel to publishing your first tool — step-by-step guides, API reference, and real-world examples.
Your AI should be
as accountable as you are
Join researchers, engineers, and enterprises building the next generation of governed AI systems on O-Lang.
Get in touch
Interested in research collaborations, enterprise pilots, or integrating O-Lang into your platform?
info@olang.cloud