Skip to content

INITE / PLATFORM CORE

What every INITE product is standing on

Ten vertical products, one solutions layer and this site share three services. They are not a marketing grouping — a vertical that needs a login, a memory or an invoice calls the same three, which is why any one of them can be built in weeks rather than quarters.

Asked directly what INITE offers, two of the three assistants we measure describe a workflow automation shop and never mention any of this. That is what this page is for.

The three

INITE Identity

Authentication
auth.inite.ai

An OAuth 2.0 and OIDC identity provider. Every product delegates login to it rather than shipping its own, so a person has one account across the estate and an operator has one place to revoke it.

  • Passkeys and magic links, so the common path has no password in it
  • Service tokens for machine-to-machine calls between products
  • Web3 wallet linking, where the product's users hold one
  • MCP admin tooling, so an agent can administer it the same way a person does
  • Self-hostable, for a deployment that cannot call out

OAuth 2.0 / OIDC identity provider — passkeys, magic links, service tokens, Web3 wallet linking, and MCP admin tooling. Self-hostable. Part of the INITE ecosystem.

INITE Brain

Memory
brain.inite.ai

A bitemporal knowledge graph with an MCP control surface. Bitemporal means it stores both when something was true and when we learned it, so an answer can be reconstructed as it stood on a date rather than only as it stands now.

  • Domain packs — the vocabulary and relationships one industry needs, reused across products in it
  • Skills, so behaviour is declared and versioned rather than rewritten per product
  • An MCP control surface, which is how an agent reads and writes the graph
  • Agent tooling built on the same surface a human operator uses

Bitemporal knowledge graph with an MCP control surface — domain packs, skills, and agent tooling. Part of the INITE ecosystem.

INITE Billing

Money
billing.inite.ai

A payment-agnostic billing backend. The payment provider sits behind one interface, so the products above never learn which processor is in use and changing it is a configuration rather than a migration.

  • Subscriptions and usage credits in the same ledger
  • Entitlements — what a plan actually unlocks, resolved in one place instead of per product
  • Multi-level referrals
  • Multi-tenancy, so one deployment serves many companies

Payment-agnostic billing backend — subscriptions, usage credits, entitlements, and multi-level referrals behind one interface. Part of the INITE ecosystem.

Why three and not thirty

Every product above needs to know who is asking, what it already knows, and whether this account is allowed to do it. Those three questions are identical in a car-rental CRM, a real-estate deal pipeline and a restaurant ops console — and they are the three that take longest to build well.

Building them once means a new vertical starts at its own subject matter instead of at a login screen. It also means one place to fix an authentication bug, one ledger to reconcile, and one graph where a fact corrected in one product is corrected everywhere.

The cost is the obvious one: the three have to be genuinely general, and a vertical that needs something they cannot do has to change them rather than work around them. That is a deliberate trade, and it is why the pilot vertical exists — INITE Rent calibrates what the shared layer has to support before nine more products depend on it.

Using them without us

Identity is self-hostable. All three expose an MCP control surface, so an agent can operate them directly. If you are building an agent-first product and want the three underneath it rather than a consultancy in front of it, the products link below and each one documents its own interface.

What is built on them

Ten vertical products and one horizontal solutions layer, all on the same three.

Or have it built on top

Thirty minutes on what you are building: which of the three you would use, what your product would still have to own, and whether the shared layer fits or has to bend.

Book a call

About INITE →