Disjoint, Inc.
Disjoint is building Closure, open-source infrastructure for pricing, metering, entitlements, and billing for AI and agentic products. Its stated goal is to make billing changes reversible and legible, keep metering in the hot path, and let finance, sales, customer success, growth, and engineering act on usage data.
At a Glance
- Founders and operators of AI and agentic software products
- B2B SaaS teams with usage-based or credit-based pricing
- Finance, sales, customer success, growth, and engineering teams managing usage-linked monetization
AI Tools by Disjoint, Inc.
(1)Closure
Open Source AI Usage Metering
Discussions
No discussions yet
Be the first to start a discussion about Disjoint, Inc.
Latest News
Disjoint publishes the Closure launch memo, explaining its mission, open-source MIT approach, founders' background at Clay, and invitation to an alpha program.
Disjoint publishes its broader GitHub repository with the 'Build with trust' positioning.
Closure repository records the first pass of the web UI.
Closure repository documents its MIT license and setup-assistant materials while continuing active development.
Products & Services
MIT-licensed, open-source pricing, metering, entitlements, and actions infrastructure for AI products. Apps send meter events and balance checks to an API; events are recorded in Redis, flushed to Postgres, and threshold events can trigger notifications and workflows. It can be used through a guided alpha or self-hosted with Docker.
Market Position
Closure positions Disjoint as an open-source, MIT-licensed and self-hostable alternative to complex, tightly coupled billing and entitlement systems. Its differentiators are reversible/versioned changes, replayable history, low-latency metering in the hot path, and cross-functional usage actions rather than billing being owned only by engineering.
Leadership
Founders
Lele Xu
Cofounder of Disjoint and co-creator of Closure; the Closure launch memo says Lele and Colin left Clay to build infrastructure for the AI economy. LinkedIn search results identify Yale University education (Applied Physics, minor in Fine Art) and a prior cofounder/CTO role at Sillable.
Colin Parsons
Cofounder of Disjoint and co-creator of Closure. He was a software engineer at Clay for two years focused on integrations and datasets, previously the founding software engineer at a property-tech startup, and earlier founded an AI-content startup; his personal site also records work at Contrary and internships at Delinea and a VR startup acquired by Google.
Executive Team
Lele Xu
Cofounder
Former Clay team member and prior cofounder/CTO of Sillable according to LinkedIn search results; Yale-trained in applied physics and fine art.
Colin Parsons
Cofounder
Former Clay software engineer focused on integrations and datasets; previously founding software engineer at a property-tech startup and founder of an AI-content startup.
Founding Story
The founders say they left Clay after seeing how difficult it was to change pricing tiers, migrate or grandfather customers, and rewrite critical access and payment systems. They started Disjoint to build infrastructure for the maximum number of people selling in the AI economy, centered on the belief that agentic products need precise, low-latency, versioned, and reversible pricing and metering.
Business Model
Revenue Model
The public offering is open-source and MIT licensed, with a guided collaborative alpha for selected teams and a self-hosted Docker deployment. The public materials do not describe a paid subscription or usage-pricing schedule.
Target Markets
- Founders and operators of AI and agentic software products
- B2B SaaS teams with usage-based or credit-based pricing
- Finance, sales, customer success, growth, and engineering teams managing usage-linked monetization
- AI and agentic products that meter tokens, actions, credits, or other usage
- Finance teams automating invoices and reconciling revenue with usage costs
- Growth teams managing promotions, coupons, referrals, and lifecycle data
- Sales and customer-success teams creating custom deals and receiving usage alerts
- Engineering teams enforcing access blocks before charges occur
- Teams migrating from complex or tightly coupled billing engines