Skip to content

Ecosystem

One CORE. Several domains.

Each 2finity domain is an interface or a service on the same CORE. Two are live, the rest are planned, and this page says which is which.

Now

The domains that define the ecosystem

2finity.com is the canonical home of CORE and the identity authority. 2finity.dev is the developer platform and runs the System Migrator. 2finity.chat, conversational control of the organization, and 2finity.network, professional and business networks between COREs, are planned.

  • 2finity.comLive

    CORE

    Canonical home of 2finity CORE

    The model, the capability contract and the identity layer.

    Open 2finity.com
  • 2finity.devLive

    Developer platform

    Builders, System Migrator, tooling

    Developer services and the System Migrator; interim operator sign-in for developer tools.

    Open 2finity.dev
  • 2finity.chatPlanned

    Conversational control

    Human, agent and company communication

    Talk to the organization; CORE stays the authority.

  • 2finity.networkPlanned

    Networks

    Professional and business networks

    Networks between organizations that choose to connect their COREs.

2finity.chat, simulated

What conversational control looks like when CORE stays the authority: a message becomes an intent, the intent a capability, and a human approves before anything changes. The domain is planned; nothing here is connected.

2finity.chatSimulated

Example commands

  • “Change the homepage headline.”site.content.update
  • “Create an invoice for Nordit.”invoice.create
  • “Give Martin permission to edit the website.”permission.grant
  • “Show me leads from Germany this month.”lead.list
  • “Publish the RTX PRO 6000 product.”catalog.product.publish
  • “Build a landing page for Iceland.”page.create
  • “Rollback yesterday's homepage change.”deployment.rollback

Simulated conversation in 2finity.chat. The user writes: “Change the Octoserver homepage headline to 'AI infrastructure without compromise.'” Website Agent answers with a proposal for octoserver.com, Homepage, Hero. Current: “GPU Infrastructure Built for AI” Proposed: “AI infrastructure without compromise.” The proposal offers Preview and Approve. Result: Approved · Published, revision #184, undo available.

Illustration of an approval step. The controls are not interactive.

Simulated conversation. Nothing is executed.

Later

Planned additions

2finity.cloud for managed CORE deployments, 2finity.ai for the agent runtime and its policies, and 2finity.work for everyday work applications on CORE. None of them exist yet; they are listed so the shape of the whole is visible.

  • 2finity.cloudPlanned

    Managed infrastructure

    Hosted CORE

    CORE deployments operated by 2finity.

  • 2finity.aiPlanned

    Agent infrastructure

    Agent runtime and policy

    Runtime, policies and tooling for agents that act through CORE.

  • 2finity.workPlanned

    Work applications

    Everyday work on CORE

    Tasks, approvals and documents as applications on top of CORE.

Structure

How they relate

CORE sits in the middle. Every domain reads and writes through the same capability contract, authenticates through the same identity and leaves events in the same audit log. A domain is a view with a purpose, not a separate product with its own backend.

2finity.com (Live), 2finity.dev (Live), 2finity.chat (Planned), 2finity.network (Planned), 2finity.cloud (Planned), 2finity.ai (Planned) and 2finity.work (Planned) connect into CORE (one capability contract).

Illustration

Principles

Four lines

The ecosystem follows four lines, one for each of the domains that define it today.

  1. 01CORE stores reality.
  2. 02Apps interface with it.
  3. 03Agents operate on it.
  4. 04Networks connect consenting COREs.