Skip to content

INITE / PLATFORM CORE

What every INITE product is standing onand why there are only three of them

Eleven products and this site stand on three services: a way in, a memory, and money. That is not a tidy way to group them — a vertical that needs a login, a history or an invoice calls the same three, which is why one is built in weeks rather than quarters.

ARCHITECTURE / WHAT STANDS ON WHATINITE registry

Verticals10

  • Rentpilot
  • Estate
  • Shop
  • Health
  • Digital
  • Studio
  • Fund
  • Food
  • Travel
  • Sport

Solutions layer1

  • Solutions

Core3

  • Identityauth.inite.ai
  • Brainbrain.inite.ai
  • Billingbilling.inite.ai

11

products standing on top

3

services carrying them

One product is marked. INITE Rent gets what will later be shared first, and hits what the shared layer cannot do yet first.

Read from the registry, not typed11 / 3

The three

The threeauth · brain · billing

  • INITE Identity

    The way in
    auth.inite.ai

    OAuth 2.0 and OIDC. Every product hands its login here 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
    • An MCP admin surface: an agent administers it the way a person does
    • Runs on your own hardware, for a deployment that cannot call out

  • INITE Brain

    The memory
    brain.inite.ai

    A bitemporal knowledge graph. It stores not only what is true but when we learned it — the difference is drawn below, because it is the part that sounds like nothing and changes everything.

    • Domain packs — the vocabulary one industry needs, reused by every product in it
    • Skills: behaviour is declared and versioned rather than rewritten per product
    • An MCP surface, which is how an agent reads and writes the graph
    • Agent tooling on the same surface a human operator works through

  • INITE Billing

    The money
    billing.inite.ai

    The payment provider sits behind one interface. The products above never learn which processor is in use, so changing it is a configuration rather than a migration.

    • Subscriptions and usage credits in one ledger
    • Entitlements — what a plan unlocks, resolved in one place instead of per product
    • Multi-level referrals
    • One deployment serving many companies at once
WHAT BITEMPORAL MEANSmodel

When it was true

1 Mar

What the graph held

$54
$50
12 Jun3 Aug
  1. 1 MarWhen it was true
  2. 12 JunWhat the graph held$54
  3. 3 AugWhat the graph held$50

2

clocks on every fact

  • What was the rate in April? — $50.
  • What did we believe the April rate was? — nothing in April, $54 in July, $50 from August.

The figures are a model, not a customer record. The point is the gap between the rows: for three months the graph knew nothing, for two it knew the wrong thing, and from August it holds the right answer and the memory of what it held before.

An ordinary database keeps one of these rows2

Why three and not thirty

Every product above has to know three things: who is asking, what is already known, and whether this account is allowed to do it. A car-rental CRM, a property deal and a restaurant console ask the same three — and those are the three that take longest to get right.

Built once, they mean a new vertical starts at its own subject matter rather than at a login screen. One place to fix an authentication bug, one ledger to reconcile, and a fact corrected in one product corrected everywhere.

The cost runs the other way: the three have to be genuinely general. A vertical that needs something they cannot do has to change them rather than work around them, and that is a change made with the other ten products standing on it. Which is exactly why the pilot exists — INITE Rent reaches the edges first, while the price of being wrong is one product and not ten.

Using them without us

Identity runs on your own hardware. All three expose an MCP control surface, so an agent operates them directly rather than through an interface of ours. 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 documents its own interface.

What stands on them

Ten vertical products and one horizontal solutions layer. The order comes from the registry; the links go to the products themselves.

Or have it built on top

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

Book a call

One company. A solutions layer. Shared infrastructure underneath.

INITE finds the operational problem, INITE Solutions turns it into a reusable working system, and vertical products carry that system into a specific industry.

  1. 01Company and transformation

    INITE

    Business-level diagnostics, INITE Protocol, architecture and one accountable commercial relationship.

  2. 02Horizontal solutions layer

    INITE Solutions

    Single-process audit, agent workflows, integrations and productized implementation across industries.

  3. 03Industry systems

    Vertical products

    Rent, Estate, Shop, Health and other domain systems built from the same platform foundation.

Every system shares three primitives.

These are operating products, not decorative sub-brands. Together with the runtime, they let solutions and verticals reuse identity, organizational memory and commercial permissions.

INITE Runtime

MCP, skills, execution, observability and shared @inite/* packages connect the three primitives to each solution and vertical product.

Start from the decision you already have.

You do not need to understand the whole ecosystem first. Pick the question closest to your situation and continue on the right surface.

About INITE →