Adapt the platform to a department without waiting for a release.
A signed extension pack brings your own dashboards, reaction rules, corporate identity, vocabulary and even one of your own web applications into AANCER, and can be removed again cleanly. Everything in a pack is data checked against a schema. Nothing in it runs with platform privileges.
Data you install, not code we ship.
Until now, adapting AANCER to a department meant asking for a change. From release r1.8 on, most of that adaptation is a pack you import, activate with your own parameters, upgrade, roll back, or retire.
Results your people can read
Workflow, agent and chat results land in typed datasets with mandatory retention, described in your own vocabulary as dimensions and measures, and shown on published, versioned dashboards. Draft with AI proposes widgets and refuses a measure it cannot find. Charts cross filter each other, tables resize, freeze and search, and a dashboard works on a tablet or a phone.
Your process reacts to what happens
A completed run, a decided approval, published rows, an ingested document, a provisioned user: eight platform events can start a workflow or an agent after the fact, with filters, retries and a dead letter you can retry. Handlers keep every governance rule they already have.
Results people can act on
An agent answers with a real table, chart or KPI card instead of prose, and you pin it to a dashboard. A form on a dashboard starts a workflow or agent with the submitter recorded. Buttons on a table start a handler with the rows you clicked.
Your colours, fonts and words
Design tokens per theme, self hosted fonts, logos, the login page and invitation emails, all as data. Every colour pair is checked against WCAG 2.1 AA before activation. Locale overlays replace shipped strings with your department's vocabulary in English, German, Spanish and Arabic.
A dashboard for someone without a login
A read only, expiring, revocable link to a published dashboard. Rate limited, never able to trigger a connector call, and every creation, revocation and view is audited with the reader recorded as an external recipient. Licence gated.
Your own application, inside the platform
A web application you already run appears in the Dashboards hub with single sign on. The app declares its capabilities from a closed list, an administrator approves them and the hosts it may reach, and every use is audited with the app recorded as a data recipient. Licence gated.
Signed, validated, reversible.
Only signers you trust
The platform verifies an Ed25519 signature and the hash of every file before storing anything. Packs may be signed by the platform, by your installation's own key, or by a partner key you add. An unknown signer is refused with a clear reason. Private keys never touch the platform.
Data, checked against a schema
Every item is validated against a versioned schema. That is what lets a pack survive platform upgrades, and what makes it impossible for a pack to smuggle in code that runs with the platform's privileges.
Upgrade, roll back, retire
Import a newer version and activate it; roll back to any imported version; retire the pack and the stock product returns. Rows are kept for audit. Every import, activation, rollback, retirement and trust key change is an audit event.
The same rules as everything else
Datasets carry retention, quotas, legal hold and erasure. Hooks run under the roles, passports, approvals and sovereignty rules their handlers already have. Embedded apps get short lived tokens bound to user, workspace and origin, revoked with the session.
Unattended installs
Packs placed in the packs directory before first boot are imported automatically, with parameters read from a file, for air gapped sites and reproducible environments. A pack can also ship JavaScript or Python functions that run in an isolated runner with no network, and navigation links and home cards of its own.
Available in every edition
Packs, dashboards, hooks, forms, frames, themes and locale overlays ship in every edition, including EVAL. Share links and embedded apps are licence gated; enabling them is a re issued licence, not a redeployment.
The next department specific wish is a pack, not a fork.
See a pack imported, a dashboard drafted from a sentence, and a hook fire on a published dataset, on your own infrastructure.