AI-native CRM infrastructure

CRM infrastructurefor AI agents.

Structured memory for contacts, companies, deals, activities, and notes - exposed through SDK, API, CLI, and MCP.

Agent memory trace

Live
Tenant org_acmeTrace ID trc_01J8ZK2Q9Y9E

tool_call

contacts.create

agent_sales -> write

ok
scope contacts:write

contact

cnt_01J Ada Lovelace

email ada@example.com

ok
scope companies:write

company

cmp_01J Analytical Engines Ltd

linked to contact cnt_01J

ok
scope deals:write

deal

deal_01J Proposal Sent

pipeline default -> proposal

ok
scope activities:write

activity

act_01J intro email logged

type email, contact cnt_01J

ok
boundary enforced

tenant

org_acme isolated

no cross-org record reads

ok
route verified

surface

MCP -> API -> Core

one auth contract, one entity model

ok
All writes committed within tenant boundary.
  1. MCPtyped handoff
  2. APItyped handoff
  3. Coretyped handoff
  4. Tenant boundaryorg_acme

Embeddable. Multi-tenant. Agent-safe. MIT licensed.

git clone https://github.com/sharonds/orbit-ai.git && cd orbit-ai && pnpm install && pnpm -r build
Your data
Isolated by tenant
Typed records
Predictable schema
Developer-first
SDK, API, CLI, MCP
Infra you control
Deploy anywhere

Shared surface area

One model, four ways in.

Choose the interface that fits your runtime. The auth contract, typed records, and tenant model stay the same.

Architecture

Records agents can trust.

Orbit gives agents a structured CRM memory layer without turning your application into a hosted SaaS dependency.

01

Shared entity model

Contacts, companies, deals, activities, notes, tasks, users, tags, webhooks, imports, and more share ID conventions, CRUD contracts, and cursor pagination.

02

Boundaries are part of the model.

Every request resolves an organization context. API keys carry scopes, records stay inside their tenant, and DirectTransport is reserved for trusted code.

03

Deploy beside your app

Run Orbit packages with your own API, adapter, and datastore. Keep auth, rate limiting, and data ownership inside your infrastructure.

Built by

Source-first CRM infrastructure from the builder behind Jobot.

Sharon Sciammas

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

Install 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.

Copy status: ready
git clone https://github.com/sharonds/orbit-ai.git && cd orbit-ai && pnpm install && pnpm -r build

Roadmap

Memory first. Research and activation next.

01

Memory is live

Typed CRM records, auth-aware surfaces, cursor pagination, SDK transports, and MCP tools are the alpha foundation.

02

Research direction

Richer enrichment and retrieval paths can layer on top of the same tenant-safe records.

03

Activation direction

Sequences, tasks, webhooks, and connector events point toward agent-driven follow-up without losing control of the data plane.

FAQ

Questions before you build on Orbit.

Short answers for teams evaluating Orbit as deployable CRM infrastructure, not another hosted CRM account.

What is Orbit AI?

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.

Is Orbit AI a hosted CRM?

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.

Is it on npm yet?

Not yet. The alpha is source-first: clone the repository, install with pnpm, and build the workspace locally until packages are published.

Which surfaces does it support?

Orbit supports a TypeScript SDK, REST API, CLI, and MCP server over the same entity model and auth contract.

How does tenant isolation work?

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.

Can I use it with MCP?

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.

What is alpha-ready now vs future?

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.