2FINITY CORE
The operating layer for humans, agents and companies.
CORE gives websites, applications, agents and organizations a shared foundation for identity, people, relationships, knowledge, workflows, commerce, finance, communication and data.
Select an interface or participant to see the CORE layers it uses.
Nothing selected.
- CORE
- The shared operating layer. Ten layers: Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication, Data.
- Website (interface)
- Public sites and portals that read content and catalog data and submit forms through CORE. Uses the Identity, Knowledge, Commerce and Data layers. Example capabilities: page.get, catalog.list, form.submit.
- Applications (interface)
- Internal, mobile and dashboard apps: views into CORE with the signed-in identity's permissions. Uses the Identity, Organizations, People, Workflows and Data layers. Example capabilities: customer.get, workflow.start, approval.decide.
- Chat (interface)
- 2finity.chat and other conversational interfaces: language resolved to capabilities, with approval. Uses the Identity, Knowledge, Workflows, Finance and Communication layers. Example capabilities: site.content.update, invoice.create, permission.grant.
- Agents (interface)
- Actors with their own identity, an owner and scoped permissions; every action leaves an audit event. Uses the Identity, Knowledge, Workflows and Communication layers. Example capabilities: site.publish, deployment.rollback, workflow.start.
- People (participant)
- Humans in any context: professional, employee, customer or supplier, with one identity throughout. Uses the Identity, People, Relationships and Communication layers. Example capabilities: customer.get, permission.grant, message.send.
- Companies (participant)
- Organizations that own their data, run their workflows and decide who and what may act inside them. Uses the Organizations, People, Relationships, Commerce and Finance layers. Example capabilities: organization.get, invoice.create, order.update.
- Partners (participant)
- Other organizations connected by a relationship: suppliers, resellers and agencies see what it grants. Uses the Identity, Relationships, Commerce and Data layers. Example capabilities: catalog.product.get, order.update, permission.grant.
- Enterprise (participant)
- Large organizations running CORE in an isolated deployment with their own identity provider and policies. Uses the Identity, Organizations, Workflows, Finance and Data layers. Example capabilities: permission.grant, deployment.publish, workflow.start.
Why CORE
Build interfaces. Not another backend.
Every company rebuilds the same backend: authentication, users, permissions, organizations, data models, workflows, commerce, integrations, communication, audit history. CORE provides it once. You build the interface.
Before CORE, each interface (Website, Internal app and Mobile app) rebuilds the same backend: Authentication, Users, Permissions, Organizations, Database models, Workflows, Commerce, Integrations, Communication and Audit history. With CORE, the same interfaces are views into one CORE whose layers (Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication and Data) are built once behind one capability contract.
What CORE is not
CMS
Content is one layer of ten, versioned and permission-checked like everything else.
Database
You never query it directly; every read and write is a capability with a permission check.
API gateway
Capabilities carry identity, permission and audit with them; routes do not.
Admin dashboard
A dashboard is one consumer of CORE, not the place where the truth lives.
Chatbot
Chat is one interface among many; CORE remains the authority.
The model
Ten layers. One operating layer.
Identity, Organizations, People, Relationships, Knowledge, Workflows, Commerce, Finance, Communication and Data: the shared model every interface reads and writes.
Every action in CORE starts with an identity. A person, an agent or a service authenticates once and carries that identity into every organization and role it is connected to. Identity holds credentials, sessions and the links to roles and permissions; it does not hold business data. 2finity Identity is the planned OIDC provider for this layer.
Example entities
- Identity
- Credential
- Session
- Service identity
- Agent identity
- Permission grant
- Identity link
Example capabilities
identity.currentidentity.verifyidentity.linksession.createsession.revokepermission.grantpermission.revokepermission.check
Interfaces
One CORE, many interfaces.
Website, internal app, mobile app, chat, agent, API. Apps become views into CORE.
Website, Internal app, Mobile app, Chat, Agent and API connect into CORE (ten layers · one contract).
Capabilities
Capabilities, not dashboards.
Every action is a named capability with a permission check and an event. The same authorized action can come from a UI, an API call, an agent, an automation or a chat message.
The same authorized action can originate from Interface, API, Agent, Automation or 2finity.chat.
- Identity: martin · Employee
- Permission: can(site.content.update) · allowed
- Capability: site.content.update · { page, block, value }
- Event: site.content.updated · #184
Example events, oldest first: time, event name, actor and reference.
- 12:04:11site.content.updatedwebsite-agent#184
- 12:04:12approval.decidedmartin#184
- 12:04:13site.publishedwebsite-agent#184
- 12:09:40invoice.createdmartinINV-2041
- 12:11:02permission.grantedadmineditor
- 12:15:27workflow.startedautomationonboarding
Example capabilities
page.getcatalog.listform.submitsite.content.updateworkflow.startinvoice.createpermission.grantdeployment.rollback
Agents
Agent-native by design.
CORE makes agents first-class participants in the organization. Humans and agents both have identity, permissions, relationships and auditable actions. Agents invoke capabilities. They do not get unrestricted database access.
- Intent: “Publish the RTX PRO 6000 product.”
- Identity: Website Agent · owner martin
- Permission: can(catalog.product.publish) · approval required
- Capability: catalog.product.publish
- Event / Audit: catalog.product.published · actor agent · approved by martin
Identity
An agent authenticates as itself, with an owner who is accountable.
Permissions
Granted to the agent directly, so they can be narrower than any person’s.
Audit
Every action is an event with the agent as actor and the approver when there is one.
2finity.chat
Control the organization by talking to it.
A message becomes an intent, the intent resolves to a capability, and CORE checks who is asking before anything happens. Chat is an interface. CORE remains the authority.
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.
From message to event
- Message
- Intent
- Identity
- Permission
- Capability
- CORE
- Event / result
Identity
One identity. Many relationships.
A person is a professional, an employee, a customer, a supplier, a partner, an administrator or the owner of an agent, often several at once. CORE keeps one identity and models the rest as relationships.
One identity (one login · many relationships) connects out to Professional, Employee, Customer, Supplier, Partner, Administrator and Agent owner.
Seven contexts
- Professional
- You, as yourself, across every organization you work with.
- Employee
- You inside an organization that employs you.
- Customer
- You buying from an organization.
- Supplier
- You selling to or serving an organization.
- Partner
- Your organization connected to another by agreement.
- Administrator
- You configuring an organization and its permissions.
- Agent owner
- You, accountable for an agent that acts in your name.
Authorization
Authorization is decided from Identity (who is asking), Organization (inside which boundary), Relationship (how are they connected), Role (in what capacity), Resource (on what) and Capability (doing what). The answer is allow or deny.
Migration
Bring the existing company with you.
The System Migrator on 2finity.dev discovers, extracts and maps a legacy system into CORE, then generates the website, applications and agents on top. WordPress and WooCommerce first.
The System Migrator reads WordPress and WooCommerce today; Shopify, Magento, ERP systems, CRM systems, Custom PHP and Node applications, Spreadsheets and Legacy databases are planned. It runs these stages in order:
- Discover: Crawl and inventory the legacy system: pages, products, users, forms, integrations. Output: Inventory.
- Extract: Read data through a read-only connector. Nothing is modified at the source. Output: Raw records and media.
- Understand: Classify what the records mean: content, catalog, customers, roles, processes. Output: Documented model.
- Map to CORE: Assign every record type to a CORE layer and the capabilities that act on it. Output: CORE mapping.
- Build interfaces: Generate the website, applications and agents that read and write through CoreClient. Output: Interfaces on CORE.
The result is a CORE with Website, Applications and Agents built on top of it.
Network effect
Solve it once. Reuse it everywhere.
Organizations run into the same operational problems. A capability built for one becomes available to the next, while each organization's data and permissions stay isolated.
One capability, invoice.create, is built once and runs separately in the CORE of each organization: Organization A, Organization B and Organization C. Each organization keeps its own data and permissions; nothing is shared between them.
Deployment
One CORE contract. Deploy it anywhere.
Managed by 2finity, private, isolated for enterprises or on your own hardware: the capability contract stays the same. Direction, not a product you can order today.
Deployment modes, each a direction rather than a product you can order today:
- Managed by 2finity (Direction): CORE operated by 2finity, one organization per tenant. Isolation: Logical, per organization. Identity: 2finity Identity.
- Private deployment (Direction): A dedicated CORE for one organization on infrastructure 2finity runs for it. Isolation: Dedicated instance. Identity: 2finity Identity or your OIDC provider.
- Enterprise isolated (Direction): Dedicated network, storage and keys; your identity provider; your audit export. Isolation: Network and data. Identity: Your OIDC provider.
- On-premise (Direction): CORE in your own data center. Same contract; you operate it. Isolation: Physical. Identity: Your OIDC provider.
Every mode runs the same CoreClient contract: identity, entities, capabilities, permissions and events.
Get started
Connect your company to CORE.
Read how CORE is structured, or start building on the developer platform.