Shared entity model
Contacts, companies, deals, activities, notes, tasks, users, tags, webhooks, imports, and more share ID conventions, CRUD contracts, and cursor pagination.
AI-native CRM infrastructure
Structured memory for contacts, companies, deals, activities, and notes - exposed through SDK, API, CLI, and MCP.
tool_call
contacts.create
agent_sales -> write
contact
cnt_01J Ada Lovelace
email ada@example.com
company
cmp_01J Analytical Engines Ltd
linked to contact cnt_01J
deal
deal_01J Proposal Sent
pipeline default -> proposal
activity
act_01J intro email logged
type email, contact cnt_01J
tenant
org_acme isolated
no cross-org record reads
surface
MCP -> API -> Core
one auth contract, one entity model
Embeddable. Multi-tenant. Agent-safe. MIT licensed.
git clone https://github.com/sharonds/orbit-ai.git && cd orbit-ai && pnpm install && pnpm -r buildShared surface area
Choose the interface that fits your runtime. The auth contract, typed records, and tenant model stay the same.
TypeScript server code
Use HTTP mode against a running API, or DirectTransport in trusted server-side contexts.
import { Orbit } from '@orbit-ai/sdk'
Any language over HTTP
REST, JSON, standard bearer auth, version headers, scoped API keys, and structured errors.
Authorization: Bearer orb_...
Shell automation
Script CRM operations from terminals and CI with orbit contacts, deals, tasks, and search.
orbit search "ada lovelace" --entity contacts
Agent tool hosts
Expose 23 built-in tools to Claude, Cursor, Copilot, and other MCP-compatible clients.
Tool: move_deal_stage
Architecture
Orbit gives agents a structured CRM memory layer without turning your application into a hosted SaaS dependency.
Contacts, companies, deals, activities, notes, tasks, users, tags, webhooks, imports, and more share ID conventions, CRUD contracts, and cursor pagination.
Every request resolves an organization context. API keys carry scopes, records stay inside their tenant, and DirectTransport is reserved for trusted code.
Run Orbit packages with your own API, adapter, and datastore. Keep auth, rate limiting, and data ownership inside your infrastructure.
Built by
Sharon Sciammas
Built by Sharon Sciammas, the developer behind Jobot, as open-source CRM infrastructure for agent workflows. Alpha, source-first, and designed to run beside your app.
Source-first alpha
Packages are not on npm yet. Until publish, clone the source and build the workspace locally.
Try from source before npm publish
No hosted backend. Build and deploy beside your app.
git clone https://github.com/sharonds/orbit-ai.git && cd orbit-ai && pnpm install && pnpm -r buildRoadmap
Typed CRM records, auth-aware surfaces, cursor pagination, SDK transports, and MCP tools are the alpha foundation.
Richer enrichment and retrieval paths can layer on top of the same tenant-safe records.
Sequences, tasks, webhooks, and connector events point toward agent-driven follow-up without losing control of the data plane.
FAQ
Short answers for teams evaluating Orbit as deployable CRM infrastructure, not another hosted CRM account.
Orbit AI is open-source CRM infrastructure for agent workflows: typed entities, a REST API, TypeScript SDK, CLI, MCP server, and connector-ready packages you deploy with your app.
No. Orbit is not a hosted product or vendor account. It is MIT-licensed source you run beside your own application, auth, datastore, and deployment boundary.
Not yet. The alpha is source-first: clone the repository, install with pnpm, and build the workspace locally until packages are published.
Orbit supports a TypeScript SDK, REST API, CLI, and MCP server over the same entity model and auth contract.
Requests resolve an organization context from the API key or trusted DirectTransport context. Application-layer checks keep records scoped to that org; SQLite is not recommended for multi-tenant production.
Yes. The MCP package exposes 23 built-in tools for MCP hosts. HTTP transport uses bearer auth per request; stdio transport reads ORBIT_API_KEY for the server process.
Alpha-ready pieces include typed CRM records, CRUD/list flows, auth-aware API routes, SDK transports, CLI commands, and MCP tools. Future work includes multi-instance stores, richer connector workflows, and completed batch mutations.