Applications That Flex Like a Custom Build and Evolve Like a Platform

Define a business object once in Stack9 Core — a claim, a case, a policy, a piece of inventory — and the data structures, REST API resources and default screens are generated for you. Then power users configure on top of it, and developers are reserved for genuinely new capability.

Read the Core Docs Explore Stack9 Core

Between a Packaged Product and a Custom Build

Your domain, modelled natively

Policies, claims, cases and employer relationships become first-class business objects — not generic content, and not custom code bolted onto a framework. Every entity you define automatically produces standard REST API resources on your own instance endpoint.

Workflow as configuration

Record Workflow Rules express states, triggers, conditions and actions. Service requests, approvals and case handling become trackable records with status and ownership, rather than logic buried in a codebase.

One connector interface, many systems

Connectors register REST APIs, direct database connections and other protocols behind a single consistent pattern — so developers work against one interface instead of a different integration approach per external system.

AI agents on your business logic

Stack9 AI Agents runs on Amazon Bedrock AgentCore and reaches beyond content into CRM, ERP, finance and HR — with every function call secured through your own identity provider, and AI processing inside the AWS Sydney region.

Built for real transaction patterns

Event-driven processing is a first-class pattern, on AWS SQS and EventBridge. Stack9 clients process thousands of recurring card transactions monthly with automatic fail, retry and manual-review handling — not manual reconciliation of every cycle.

Speed inside your governance, not around it

Changes made in Stack9 Console are still raised, reviewed and deployed through a formal Request for Change process. Low-code improves delivery speed within change control; it does not replace it.

How an Application Comes Together

1

Model the domain

Define entities once. Stack9 generates the tables, the REST API resources and a default set of screens to work against immediately.

2

Configure behaviour

Workflow states, automations, a query library for reporting, document templates and permissions — all configured through Stack9 Console rather than written.

3

Connect the systems of record

Register each external system as a Connector. Where several systems are involved, AWS API Gateway consolidates them so your entities interact with one governed interface.

4

Build the genuinely new once

A new UI component, a new entity type or a first-time data source connection is engineering work. After it is built once, it joins the library for configurators to reuse without further code changes.

Applications on Stack9 Core

Case management, complaints triage and operational systems.

Authenticated case management portal with an AI agent triaging and routing incoming complaints — CCHP (Queensland Government) — a fully functional proof of concept in which an AI agent triages and routes incoming public complaints to the correct department, inside an authenticated case-management portal. AI operating on real business logic, not marketing content.

Stack9 Console entity configuration screen showing fields, relationships and workflow states — Stack9 Console — entities, screens and automations configured visually, then deployed through formal change management.

Eagers Automotive — inventory management as part of a wider Dealership Experience Platform, in partnership since 2020.

A Custom Build Cannot Evolve. A Packaged Product Cannot Flex.

Stack9 sits deliberately between the two — and brings RBAC, row-level security, audit trail, document management, email, autoscaling infrastructure and an upgrade path that a custom build would have to construct and then maintain forever.

Start in the Docs Why Stack9