Alliance Business Suite
One operating system for your entire business.
Run finance, customers, commerce, projects, workforce, procurement, payments, documents and workflows on one extensible business platform. Nucleus Web is the AI-first way to use it: ask what changed, understand why, and coordinate what happens next.
34 platform engines2,900+ business operations76+ connected systems
The fulfilment delay is what put the payment and the relationship at risk, not the other way round.
Recovery started
What Nucleus Web brought together
Customer health
At risk
Order
SO-4417
Shipment
9 days late
Open invoice
$48,210.00
Payment status
62 days over
Support history
2 cases, no reply
Every step stayed inside your organization, your permissions and your policies.
Customer health
At risk
Order
SO-4417
Shipment
9 days late
Open invoice
$48,210.00
The fulfilment delay is what put the payment and the relationship at risk.
The problem
Nobody manages a business. They manage tabs.
Slack, Excel, SAP, QuickBooks, Notion, Drive, email, HubSpot, Stripe. The work is real, and almost none of the day is spent doing it. Businesses do not have an AI problem. They have a fragmentation problem, and one more application does not solve it.
Today
With Nucleus Web
- Find the right application
- Start with the situation
- Reconstruct the context
- Keep the context together
- Remember to run it
- A schedule or an event runs it
- Coordinate every handoff
- Bring in the right people and systems
- Track what happened
- Retain the result and evidence
The system underneath
One business. One operating system.
Customers, finance, commerce, projects, documents, people and payments should not behave like separate products. Alliance Business Suite holds them in one governed system that shares identity, permissions, data and context.
Ways to operate it
Studio
Configure and govern
Nucleus Web
Operate day to day
Workflows
Coordinate the work
Agents
Reason over it
API and MCP
Integrate with it
Modules
Extend it
Governed business capabilities
abs.projects.storage.read
Every surface above calls the same declared capability. Its permission, its effect and its risk travel with it, so governance is not rebuilt once per interface.
Platform engines
- Accounting and finance
- Payments and wallets
- Billing and subscriptions
- Commerce
- Sales and POS
- CRM
- Marketing
- Projects
- Workforce and HR
- Logistics and supply chain
- Procurement
- Manufacturing
- Quality
- Assets
- Content and CMS
- Regulated documents and UBL
- Signatures and eSign
- Analytics
- Workflow and automation
- Identity and federation
- Security and access
- Cognitive and AI
- Education and LMS
- Support and helpdesk
- Social
- Portals
- Licensing
- Healthcare
- Blockchain
- Workplace
- Sustainability
- Partners
Accounting, commerce, CRM, projects, logistics, workforce, documents, analytics, payments, workflows and more. Separate systems that share one identity, one data model and one execution model.
One business model. Many ways to operate it.
Nucleus Web keeps the whole situation together
One · Understand the situation
See what changed, and what it means.
Bring together the facts and evidence that explain what is happening. Nobody should have to assemble that picture by hand before they can act on it.
Learn more about how it worksThe most important questions rarely respect department boundaries
Evidence · Shipment SH-8841
Hover to inspect
- Promised
- 14 May
- Delivered
- 23 May
- Carrier
- Held at hub
- Signed for
- Yes
Shipment records, confirmed with the carrier
- StartSTART
- Collect open invoicesSERVICEQUERY
- Over 60 days?CONDITION
- Notify the account ownerSERVICECOMMAND
- Write the review offSERVICECOMMAND
Two · Coordinate the response
Coordinate what happens next.
Bring people, agents, workflows and systems into the same process. Each step records what it did before the next one starts, and a step that fails takes the branch its author wired for exactly that.
- Processes continue after you leave
- A step that fails is caught, not swallowed, and says why
- Progress and evidence stay attached to the work
Three · Work that starts without you
Nobody has to remember to run it
A process starts on a schedule, or on something the business actually did: a contract sealed, a contact created. It runs on permissions granted to it rather than borrowed from whoever was last at a desk, and you watch it move a node at a time while it happens.
Triggers
- When
- Every weekday at 07:00, America/Bogota
- Runs
- Receivables review, published v4
- As
- Receivables Automation
- Rule
- Do not start if the last one is still running
- When
- On trust.signed-document-signed, v1
- Runs
- Customer onboarding, published v3
- As
- Onboarding Automation
- Rule
- Only for documents on a customer agreement
A trigger points at an exact published version. Moving it to a newer one is a decision somebody makes, never something that happens quietly overnight.
Every firing, including the ones it refused
- Thu 07:00Startedrun 8f21c4
- Thu 06:42Loop blockedthe event came from a run this same trigger started
- Wed 07:00Skipped overlapthe previous run had not finished
- Tue 07:00Deniedthe application no longer holds projects_read
- Mon 07:00Startedrun 6ab233
A refusal is written down as carefully as a run. Nothing is dropped silently, so the week a permission was revoked is answerable a year later.
- Start
- Collect overdue invoices
- Group by cause
- Notify the account owner
- Record what it could not close
- It runs as an application, not as you
- Unattended work has its own identity, its own enrollment and its own grants. Nobody leaves a personal account signed in overnight. Only the coordinates of that identity are stored, never a snapshot of what it was allowed to do, so it is resolved again on every single firing and a grant revoked on Tuesday bites on Wednesday.
- Authoring a trigger is not permission to run one
- Changing what fires, and when, needs workflows_manage_triggers. Running a workflow needs workflows_execute. Two separate grants, so the person who designs the automation is not by that fact the identity that carries it out.
- It will not start itself in a circle
- A run stamps its own causality onto anything it raises, and the depth strictly increases at every hop. A trigger will not fire on an event its own run emitted, and a chain that passes its ceiling is stopped. Neither is a silent drop: both land as a terminal occurrence naming which of the two guards fired.
Four · Go deeper when you need to
Start in Nucleus Web. Go deeper in Studio.
Continue with the same organization, permissions, record, workflow state and history. Drag the seam and watch the invoice stay exactly where it is.
INV-2231 is 62 days past due on $48,210.00. Two reminders were sent. Credit terms changed from Net 15 to Net 30 on 12 June, which is when it started slipping.
invoices_read · contacts_read · orders_read
Open in Studio
| Line | Item | Qty | Amount |
|---|---|---|---|
| 1 | Industrial relay · IR-40 | 120 | $18,400.00 |
| 2 | Control module · CM-9 | 40 | $22,110.00 |
| 3 | Installation service | 1 | $7,700.00 |
Across every system involved
Keep the work moving across every system it touches
Complete the work through Alliance Business Suite and the connected services the outcome requires, in one coordinated run.
“A strategic customer’s delivery is late and payment is at risk.”
- Customer and order contextSuite
- Carrier tracking checkedConnected
- Payment status confirmedConnected
- Recovery process startedSuite
- Customer notifiedConnected
- Revised payment plan drafted for the ownerSuite
One run, inside and outside the Suite, under the same permissions and on the same record. Each connected system contributes its own actions to that run.
- 76+
- connected systems
- 2,900+
- business operations
- 34
- platform engines
Some of these are integration platforms themselves, so the practical reach extends well past the names above.
See every integrationThe foundation
One business context underneath every interaction
Nucleus Web and Studio work over the same organization, identities, permissions, records, workflows and history. Choose any situation and watch what it assembles.
The signal
Strategic customer at risk
Delivery is late. An open invoice for $48,210 is now at risk.
What Nucleus Web brought together
- Account health and relationship value
- Order and fulfilment status
- The open invoice and its terms
- Recent support history
- Payment status with the provider
Reaching Carrier tracking, Payment gateway, Email and SMS
The response it proposed
- 1Confirm the new delivery date with the carrier
- 2Contact the customer with the revised plan
- 3Draft a revised payment plan for the account owner
- 4Track the recovery through to completion
One customer protected
The customer was contacted, the delivery plan was updated, and what the run did and did not do is on the account.
One coordinated response, and what it would not do kept beside what it did.
- 34
- platform engines
- 2,900+
- business operations
- 76+
- connected systems
Every capability the Suite gains, and every action a connected system contributes, becomes something agents and workflows can use. Nucleus Web grows with it without becoming another menu to learn.
Agents and identities
Give an agent the tools to help
Choose which governed capabilities an agent may use, and see every call it makes. One catalog serves the workflow designer, the agent and the tool host, so a capability is defined once, carries its own permission, effect and risk, and answers the same way whoever calls it.
Learn more about agentsOne governed capability
abs.projects.storage.read
Read Project File Content
Reads a project file as bounded text, scoped to the acting tenant. Binary content is never inlined.
- Effect
- Read
- Risk
- Confidential
- Requires
- projects_read
- Published to
- WorkflowAIMCP
Nothing is exposed by default: a capability declares no surface until somebody gives it one. And the unit of extension is an attribute on a use case that already exists, not an adapter, which is why a capability arrives on all three surfaces at once or on none.
Acting in
- Workspace
- Contoso Technologies
- On behalf of
- Daniel Lozano
- Project
- Northwind recovery
Calls in this run
- List the files on this project9 files
- Read a project fileTerms of trade.md
- Read a conversation attachmentDelivery schedule.csv
- Post a credit notenot a capability this agent holds
The run stopped at the refusal instead of finding another way round it, and the refusal is part of what the run kept. A capability classified above what the actor may perform is refused, not attempted.
Files hang off the record they belong to. A document is found through the invoice, the project or the conversation it was attached to rather than through a folder somebody named in 2019, and an agent reading one is making the same governed call, under the same permissions, that you would.
- People and applications are not one list
- Somebody joins by invitation, and the invitation stays as the record of how they got here. An application identity is provisioned instead, granted only the actions it needs, and suspended on its own. A permission covering a whole family is refused outright: grant the specific ones.
- Roles you were shipped, roles you wrote
- The platform's own roles and permissions are marked as the platform's and cannot be renamed or removed. The ones your workspace authored are marked as yours, and they are the ones it is free to change.
- One launcher over everything published
- Twenty one Studio modules across fourteen categories on the reference deployment, listed from what the runtime advertises rather than from a menu somebody maintains. A module that ships tomorrow appears on its own.
Control and evidence
Stay in control at every step
Every governed capability declares what it does, what it risks and what it needs. The answer is the same whether a person, a process or an agent asked.
One call from the Northwind recovery, checked in full.
- Acting identity
- Daniel LozanoSigned in, not impersonated
- Organization
- Contoso TechnologiesThe only tenant in scope
- Asked for
- The open invoices on Northwind TradersOne governed capability
- It declares
- ReadAnd the permission it needs to run at all
- Permission
- Allowedinvoices_read, granted by role
- A write here
- RefusedAbove what this actor may perform
- Evidence
- RetainedWho, what, when and on whose authority