Ecosystem

Ten sectors, one foundation

ORIGIN is being designed as a shared foundation: accounts, organisations, projects, permissions and an audit trail. Ten sectors have their own purposes within it, but not every sector uses that foundation today. Not every sector has a released product, and the list below says which have even begun.

Skip the map and read the list

Interactive sector map

ORIGIN
shared foundation

Create

BINHI

BINHI is where things get made: websites, graphics and edited images in one creative workspace.

BINHI is a standalone product today. A hub for it exists inside ORIGIN, and closer integration with ORIGIN is deferred.

Product in development A product is in testing. Nothing is publicly available yet.

See the BINHI project

All ten sectors

  1. 1. BINHI · Create

    Product in development

    BINHI is where things get made: websites, graphics and edited images in one creative workspace.

    How it fits: BINHI is a standalone product today. A hub for it exists inside ORIGIN, and closer integration with ORIGIN is deferred.

    Where it stands: A product is in testing. Nothing is publicly available yet.

    See the BINHI project

  2. 2. LIKHA · Develop

    Product in development

    LIKHA is the place where software is written: an offline-first IDE and the likha command-line tool.

    How it fits: LIKHA is an independent IDE. A read-only connection to ORIGIN is being built behind a feature flag.

    Where it stands: A Windows release candidate is in testing. Nothing is publicly available yet.

    See the LIKHA project

  3. 3. TALA · Think

    Product in development

    TALA is intended to reason about work and propose what to do, leaving decisions with people.

    How it fits: TALA is an independent product with its own desktop app. Inside ORIGIN, its intelligence surfaces through an existing assistant area. Wider integration is deferred.

    Where it stands: A desktop product is being built. Release has not been granted.

    See the TALA project

  4. 4. AGOS · Automate

    Foundations only

    AGOS is meant to run the repeating parts of work: workflows, schedules and moving data between places.

    How it fits: AGOS is intended to orchestrate. Anything that changes infrastructure is intended to be carried out through LIYAB, the single audited path.

    Where it stands: A workflow contract is specified. No runtime has been released.

  5. 5. LIYAB · Operate

    Foundations only

    LIYAB operates infrastructure for the ecosystem through one audited execution path, so there is always a clear record of what happened and why.

    How it fits: LIYAB is intended to be the one place where infrastructure actions are carried out. Other sectors request; LIYAB executes.

    Where it stands: Deployment tooling exists inside ORIGIN. The sector itself has not been released.

  6. 6. ULAP · Host

    In planning

    ULAP describes the cloud resources a project needs: what exists, what is wanted, what limits apply and what is used.

    How it fits: ULAP is intended to declare and never execute. LIYAB would carry out the changes, and BARYA would bill against ULAP's metering.

    Where it stands: In planning. Its charter is a draft and no product exists.

  7. 7. LIPAD · Communicate

    In planning

    LIPAD is intended to give a business professional email under its own domain.

    How it fits: LIPAD is intended to build on the shared accounts and permissions in ORIGIN, and to rely on BANTAY and TULAY for trust and connectivity.

    Where it stands: Only a coming-soon page exists. There is no mail service.

  8. 8. BARYA · Monetize

    In planning

    BARYA is intended to let products charge for what they offer: billing, payments and subscriptions.

    How it fits: BARYA is intended to bill against the usage that ULAP measures. Any real financial action will need separate authorisation.

    Where it stands: In planning. No payment provider is connected and no payments are processed.

  9. 9. BANTAY · Protect

    In planning

    BANTAY looks after who can do what: identity policy, permissions and trust across the ecosystem.

    How it fits: BANTAY is intended to work on the shared foundation and never to be a second identity system. Early foundations exist inside ORIGIN.

    Where it stands: The concept direction is agreed. The sector itself is in planning.

  10. 10. TULAY · Connect

    In planning

    TULAY sets the standards for how things connect: credentials, webhooks, API versions and plugins.

    How it fits: TULAY is intended to own the connection standards for the ecosystem. Owning a standard does not grant unrestricted access to anything.

    Where it stands: In planning. Early connection foundations exist inside ORIGIN.

How the sectors fit together

This is the intended design. Some sectors request, some declare and one executes: TALA is meant to reason and propose, AGOS to orchestrate work, ULAP to declare what cloud resources are wanted, and LIYAB to be the single, audited place where infrastructure actions are carried out.

BANTAY is intended to look after identity policy and permissions on the shared foundation, rather than creating a second identity system. TULAY is meant to set the standards for how things connect, and BARYA to bill against what ULAP measures.

Where a sector is described as in planning, it means exactly that: no product, and no promise of a date.