In an enterprise platform, a new capability is a project: a specification, a developer, a release, a regression. In Amzaa it is a wizard. The person who owns the risk configures it, and it exists the moment they hit save. Nothing to deploy, nothing for a platform team to maintain.
Everywhere else, "configurable" means a developer writes less code than usual. Here it means no code at all. A new app is a set of rows on a shared engine. The engine does not change when you add a solution; only the data does.
There is nothing to deploy, nothing to regression-test, and nothing for the platform team to inherit afterwards.
A new app from a wizard. Name it, add fields, choose types, done. No schema migration, because the schema is the graph and the graph already holds anything.
A workflow is stages you name and order. An approval is a gate you place. Governance is defined by the person who understands it, not translated by someone who does not.
An agent reads, drafts and proposes. It never writes. A human approves, the engine writes, and one switch stops every agent at once.
When an issue closes, open a review in another app. When a risk crosses a threshold, create a task. One app acts on another, with no glue code.
A field derived from other fields. An exception rate from a sample size. A residual from an inherent score and a control strength. Formulas, chosen, not written.
Every record can carry its own risk, scored from its own fields and its place in the graph. Risk is an attribute, not a separate module bolted on.
A small cohort of regulated banks, NBFCs and the firms that own them. Early access, real influence, pricing that holds.
We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.