Build anywhere.
Run on DataInbox.
APPSS is the next Datastreams route for tailored business products assembled and operated at runtime from controlled definitions, data contracts and rules.
The interface can change. The business contract and authoritative state remain.
State becomes experience
One controlled business capability can serve many interfaces.
APPSS is not a second source of business logic. It is the application contract and runtime layer through which interfaces use DataInbox state.
Forms and workspaces
Collect and change business state through explicit contracts, validation and permissions.
Portals and dashboards
Present the current state, decisions, objectives and next permitted actions to the right audience.
Operational workflows
Coordinate human and automated actions without duplicating business truth inside the interface.
Apps and experiences
Serve web, mobile and future interfaces from the same controlled business capability.
Your streams. Your APIs. Your interfaces.
Build the experience around your business.
Each stream offers an API: a controlled connection through which an application uses the information and actions your rules make available. Define that contract around your business context, then build the customer portal, employee workspace or partner service you need.
1. Your agreements define the operation
Specify the information, purpose, permissions, processing and retention. The stream executes the approved rules and records the relevant outcome.
2. The API exposes permitted capabilities
Describe what an application can request or submit and the conditions that apply. The runtime checks identity, authority and current context when processing a request.
3. Your interface shapes the experience
Choose your framework and use AI to help build the interface. Reuse the stream's contract instead of implementing the same processing rules in every screen or application.
One order, three experiences
Different interfaces. The same agreed operation.
A customer portal shows delivery progress. An employee workspace offers the permitted recovery actions. A delivery partner submits a status update. Each uses the information and actions allowed for its role, connected to the same order context and processing agreements.
If compensation requires approval, a newly built interface cannot remove that condition. The runtime evaluates the request against the approved rule, regardless of which interface submitted it.
Your business context shapes the API contract. Your interface can evolve without rebuilding the underlying processing agreements.
AI can accelerate interface development; the application still needs authentication, contract integration and testing. Connected supplier systems retain their own interface constraints. The flexibility comes from separating your business operation from those interfaces and from the screens people use.
AI-native development
Use AI to build faster without making generated code the business authority.
An interface can be created with Cursor, Claude, OpenAI, another AI coding tool or conventional engineering. It still consumes explicit contracts and permitted actions from the controlled runtime.
any builder or framework
→ APPSS application contract
→ controlled state and objectives
→ approved live operation
Clear separation of responsibilities
Build freely at the edge. Stay controlled at the core.
Application teams choose the experience; the organisation retains one definition of business state, rules, permissions and evidence.
Application team
Chooses the interface, interaction design and delivery framework.
APPSS
Exposes the controlled contracts, queries and actions the application may use.
DataInbox
Maintains authoritative state, objectives, events, rules, actions and evidence.