Why LatticeKit? · Investors & strategic partners
Operations is the largest software category nobody has consolidated.
Most platform layers of the modern stack have been captured by a clear winner. Database: Postgres. Compute: AWS. Payments: Stripe. Comms: Twilio. Identity: Auth0 / WorkOS. The exception is operations — the layer that wires scheduling, identity, money, ledger, comms, and audit into the running of an actual business. It is fragmented across hundreds of vertical SaaS products that each rebuild the same plumbing.
The thesis
Every operations-heavy business — service shops, hospitality, retail, healthcare, fitness, education, transportation — runs on the same underlying primitives: a scheduling layer, an identity layer, a money layer, a ledger, a comms layer, and an audit trail. Existing software treats each one as a product (Square, Toast, HubSpot, QuickBooks, Calendly, Twilio, Stripe). The thesis: the primitives aren't different from vertical to vertical. Only the composition is.
LatticeKit is the bet that the operations substrate becomes the next captured platform layer — that the next decade rewards horizontal primitives over vertical-by-vertical SaaS, the way AWS rewarded horizontal compute over per-stack hosting providers.
What's distinctive
- Breadth from the start. Eleven primitives live today across configuration, scheduling, resources, identity, catalog, POS orders, payments, ledger, communications, workflow, and the operator console. Three more in active phase-1 development (real-time channels, marketing, reporting, data import). One OpenAPI spec across 197 endpoints.
- AI-native authoring. The operator console (Demerzel) ships an MCP tool registry over every primitive plus an AI chat with "Apply to editor." Operators configure complex behavior in natural language; AI agents act on tenants' behalf through structured tools, not screen-scraping. Built for the world where AI is the default interface.
- Shared audit-event outbox. Every primitive writes to one stream. The same source feeds Daneel workflows, Speaker dispatch, Palver real-time push, Pelorat reporting, and Magnifico marketing — one source of truth, many consumers. This is the architectural choice that makes everything else compose.
- Opaque cross-primitive references. Primitives never foreign-key each other. Each can be deployed and scaled independently. The cost of growing a primitive doesn't compound the cost of the others.
- Built in the open. Active development, weekly visible progress (see the changelog). Design partners onboarding now.
The "why now"
Two forces converge: AI agents now need structured interfaces to operate real businesses (Model Context Protocol, audit-event outboxes, consent gates, OpenAPI contracts — LatticeKit was built natively for this), and the vertical-SaaS land grab has saturated. Operators feel the cost of duct-taping ten products together. Builders feel the cost of rebuilding the substrate every time. Both audiences want a platform layer that didn't exist when the dominant vertical-SaaS products were designed.
Where we are
- Eleven primitives live in production-shaped code, three more in phase 1.
- Operator console (Demerzel) live at latticekit.app with magic-link auth and AI chat.
- Marketing site at latticekit.tech with full primitive docs, three use-case walk-throughs, and a live OpenAPI reference.
- Early-access tenants engaging directly while the platform's rough edges are sanded.
- Public pricing, sales motion, and go-to-market team are not in place yet — we are in the build-with-partners phase.
What we want to hear from you
If you invest in or partner with infrastructure companies and the thesis resonates — or if it doesn't and you want to argue with us — we want the conversation. Use the waitlist form, note that you are reaching out as an investor or strategic partner, and we'll find a time.