Sharon Sciammas
Orbit is part of Sharon Sciammas’ open-source agent work, alongside Jobot. It is alpha, source-first, and designed to show how agent products can own their customer memory layer.
Source-first alpha
Customer memory
for AI agents.
Your agent can call any tool. But without memory, every conversation starts from zero. Orbit gives AI agents durable, structured customer context they can read, write, and trust.
Your data Isolated by tenant
Typed records Predictable schema
Developer-first SDK, API, CLI, MCP
Infra you control Deploy anywhere
Built on trusted foundations
TypeScript
Node.js
Hono
Zod
Drizzle
Postgres
SQLite
Our belief
We believe agents should remember
what matters.
By designing tools that are structured, typed, and durable, we help agents unlock deeper insights, work more autonomously, and make better decisions. With memory that adapts to real-world needs, we're shaping a future where humans and AI build together.
The problem
Every conversation starts from zero.
Agents can book meetings, send emails, and run code. But ask them about a customer from yesterday and they draw a blank. Without durable memory, agents are just stateless functions in a chat window.
Vector memory is not a CRM model
Embeddings remember semantics, not structure. Agents need typed people, companies, deals, ownership, tasks, notes, and full activity history — not fuzzy semantic blobs.
Writes need guardrails
When an agent can mutate customer data, scopes, tenant boundaries, idempotency, and structured errors stop being nice-to-haves and become product requirements.
Infrastructure you control
Orbit deploys beside your app with your auth, your adapter, and your datastore. No vendor lock-in. No "contact sales" button. Just source you own.
What it does
CRM infrastructure for the agentic era.
Orbit is not a hosted product. It is open-source packages you run beside your app — typed entities, auth, storage adapters, and agent tools that share one model.
Typed by design
Typed CRM entities
Contacts, companies, deals, pipelines, stages, users, activities, tasks, notes, products, payments, contracts, sequences, tags, webhooks, and imports. Every entity has CRUD, cursor pagination, shared schemas, and validation.
Five ways in
Multi-surface access
One entity model, five ways in: TypeScript SDK, REST API, CLI, MCP server, and DirectTransport for trusted server-side code.
Your datastore
Storage you control
SQLite via node:sqlite for local development and tests. Postgres, Supabase, or Neon for production. Switch adapters without touching your product code.
Defense in depth
Multi-tenant by design
Every record is organization-scoped. Tenant guards enforce isolation at the service layer. Postgres RLS policies add defense in depth.
Agent tools
Agent-ready MCP server
23 built-in tools for contacts, deals, activities, schema operations, imports, and more. Stdio and HTTP transports. Works with Claude, Cursor, Copilot.
Built-in safeguards
Operational protections
Bearer API keys with scoped access. Rate limiting, idempotency, structured errors, request IDs, and payload limits built in.
Watch it work
From install to intelligent agent in 25 seconds
Rendered with Hyperframes — HTML-native video composition
Proof surfaces
One memory model. Four ways in.
Choose the interface that fits your runtime. The auth contract, typed records, and tenant model stay the same.
- Write latency
- 10ms
- Local SQLite commit
- MCP tools
- 23
- Exposed to agent hosts
- Surfaces
- 4
- SDK, API, CLI, MCP
- Tenant isolation
- 100%
- Org-scoped by default
Ecosystem
Seamless integrations with your stack
Connect Orbit with the agents, databases, and tools you already use.
- OAIOpenAI
- ANTAnthropic
- CLDClaude
- CURCursor
- COPCopilot
- NJSNode.js
- TSTypeScript
- PGPostgres
- SQLSQLite
- HNOHono
- ZODZod
- DRZDrizzle
Architecture
How it works
One entity model. Four layers. Zero hosted lock-in.
MCP Hosts
InputClaudeCursorCopilot
Surfaces
ProcessMCP ServerREST APISDKCLI
Core
ProcessEntitiesServicesAuthTenant Guards
Storage
PersistSQLitePostgresRLS
Memory first. Then prove what should come next.
1
Memory is live
Typed CRM records, auth-aware surfaces, cursor pagination, SDK transports, CLI commands, and MCP tools are the alpha foundation.
2
Semantic recall comes after trust
The next memory work should start with notes, activities, and conversation artifacts where recall adds the most value.
3
Expansion follows signal
Research, ecosystem adapters, and production trust are roadmap options. The page should not pretend those are finished launch products.
Built by
Built by Sharon Sciammas.
Source-first alpha
Source-first alpha.
Packages are not on npm yet. Until publish, clone the source and build the workspace locally. No waitlist, no hosted CRM, and no npm package until publish.
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 buildFAQ
Questions before you build on Orbit.
Short answers for teams evaluating Orbit as deployable CRM infrastructure, not another hosted CRM account.
Get started
Add a CRM to your product in under an hour.
Self-hosted, typed, and agent-ready. No vendor lock-in. No per-seat pricing. Just open-source packages that work.
MIT License · TypeScript · Postgres & SQLite