Build on an AI platform you own
ibl.ai is the agentic AI platform where you own all the code and the data. Its 5 repositories are public on GitHub — the application layer, the SDK, the agent skills and MCP server, and the infrastructure CLI — so you can read the source, scaffold an app, and run the whole stack on your own cloud, on-premise, or fully air-gapped, model-agnostic across any LLM and with no per-seat pricing.
Not an API you rent — a full platform you keep. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.
$ npx skills add iblai/vibe$ npx skills add iblai/vibe --allWhich ibl.ai repositories can I read and run myself?
These 5 repositories are the platform. Most AI vendors give you an endpoint; ibl.ai gives you the source you can read, fork, run, and extend — from the app your users touch down to the infrastructure it runs on. Every card below shows the live release straight from GitHub.
The open-source platform itself. Create and deploy customizable AI agents with multi-LLM support, real-time chat and voice, document training, analytics, user management, SSO, and embeddable widgets.
Skills-intelligence platform on the same SDK — discover courses, track competencies, and earn credentials. A second complete application you can read end to end.
Scaffold a production-ready Next.js app on ibl.ai — SSO auth, AI chat, profiles, notifications, and analytics wired up out of the box, with pre-built components and Claude Code skills.
$ npx skills add iblai/vibeAn interactive CLI that provisions the whole platform on your own AWS or GCP account with Terraform and configures servers with Ansible — and it can bootstrap any existing server.
The documentation source — every page published at ibl.ai/docs, versioned in the open and available for contributions.
How do I drive the ibl.ai platform from code or an agent?
Every capability of the ibl.ai platform is a documented REST endpoint: agents, chat, users, analytics, documents, and credentials. Build integrations against it directly, or let an AI agent operate it for you through the Model Context Protocol.
Interactive API reference
Browse the full endpoint catalog with per-endpoint curl examples — generated from the live OpenAPI schema, so it never drifts from what the server accepts.
Base: platform.iblai.app
Skills & MCP server
Install the platform skills and your coding agent can run the whole system — create agents, manage users, trigger workflows — from Claude Code or any MCP client.
$ npx skills add iblai/vibe --allWhere are the deployment guides for claws and the ontology?
The guides below are mirrored from their own public repositories — self-hosted OpenClaw and NemoClaw servers, the portable .iblai agent format, and the on-premise ontology layer that makes your existing systems queryable by agents over MCP. Each one is generated from the repository, so it cannot drift from the code.
What do I actually own when I build on ibl.ai?
Rented AI is a cost that recurs forever and leaves nothing behind. An owned platform is an asset: the code, the data, and the infrastructure are yours, and they keep their value after the contract ends.
Rented AI
- Per-seat or per-token billing that scales with headcount
- Locked to one vendor's models and roadmap
- Your data lives in someone else's cloud
- Credits evaporate when the subscription lapses
ibl.ai — owned
- Full source under a perpetual license
- Model-agnostic — run any LLM, switch anytime
- Code, data, and infra stay in your environment
- Usage-based, never per-seat — yours to keep
1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University. ibl.ai is family-owned and operated from New York, NY. Explore the self-hosted platform or the full-code license.
Clone a repo and run it today
On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.
Developer FAQ
Yes — and we like to be precise about it. The application layer (iblai/os), the skills-intelligence app (iblai/lms), the developer toolkit, SDK, platform skills and MCP server (iblai/vibe), the infrastructure CLI (iblai/infra-cli), and the documentation itself (iblai/docs) are all public on GitHub.
Read them, fork them, and run them yourself — this page links each repository directly, and every documentation page under /developer is generated from the repository it documents.
There is one core platform component that isn't public open source. You can use it as a fully managed, hosted service, or take it under a perpetual source-code license and self-host the entire stack.
Either way the principle is the same: you own all the code and the data, and your deployment is yours — nothing is locked away from you.
Want to see exactly where every line is drawn? Talk to us and we'll walk you through the whole architecture.
Scaffold a production-ready Next.js app with the vibe toolkit — SSO auth, AI chat, profiles, notifications, and analytics are wired up against a hosted backend out of the box.
Then add the platform skills with `npx skills add iblai/vibe --all` to drive the whole system from Claude Code or any MCP client, and deploy agents from the claws template library.
ibl.ai exposes a full REST API for the platform — agents, chat, users, analytics, documents, credentials, and more.
The interactive API reference lives at /developer/api-reference, the OpenAPI schema is served at /api/docs-schema, and the production API base is platform.iblai.app.
The iblai/vibe repository ships agent skills plus a Model Context Protocol (MCP) server, so an AI agent can operate the entire ibl.ai platform through its REST API.
Install them with `npx skills add iblai/vibe --all` and your coding agent can create agents, manage users, and run workflows directly.
Yes. iblai/infra-cli is an interactive CLI that provisions the platform on your own AWS or GCP account with Terraform and configures servers with Ansible — and it can bootstrap any existing server.
You own all the code and the data, and the infrastructure too: cloud, VPC, on-premise, or fully air-gapped.
ibl.ai is model-agnostic. Run any LLM — Claude, GPT, Gemini, Llama, Mistral, Qwen, or your own fine-tune — and switch per workload without rebuilding your application.
You are never locked to a single vendor's models.
Every page under /developer/{repo} and /developer/guides is generated directly from the upstream GitHub repository by a sync script — the README and each file in the repo's docs directory.
That means there is no second copy to keep in sync: the engineers who ship the code write the documentation in the repo, and this site is the view. Pages that document the hosted platform backend, which has no public repository to mirror, live under /developer/platform and are maintained by hand.
Instead of per-seat SaaS, ibl.ai is usage-based or a flat perpetual license. What you build is a durable asset you own outright — not credits that evaporate when a subscription lapses.
ibl.ai serves 1.6M+ users from 400+ organizations and is family-owned and operated from New York, NY.