ApplicationsCatalog
Pick an application. It works on day one.
Four complete applications — Legal, IT, HR, and Customer Support. Each arrives with the interface, agents, skills, and integrations the work needs. Your team makes it yours, and it runs in your own cloud.

01The applications
The applications
Each one is a full product for the team that owns the work — not a chatbot with your logo on it.

Legal
Agentic Legal
Every contract reviewed against your playbook, before a lawyer opens it.
- Off-standard clauses flagged, redlines drafted
- Your lawyers keep working in Microsoft Word
- Obligations and renewals tracked after signature

IT
Agentic ITSM
The routine tickets close themselves.
- Password resets and access requests, end to end
- New-hire setup from a single request
- Escalations arrive with the diagnosis done

HR
Agentic HR
Employees get answers without opening a ticket.
- Answers grounded in your own handbook
- Onboarding and leave handled end to end
- Only the exceptions reach a person

Support
Customer Support
Cases arrive researched, with the reply already drafted.
- The customer's history pulled before an agent reads it
- Refunds and replacements staged for one click
- Churn signals flagged while there is time to act
02The alternatives
Why not a workflow builder — or building it yourself?
Workflow builders are fine for wiring two tools together. Building in-house gives you control at the cost of a year. When the work is a department's daily job — real data, real permissions, a real budget — it deserves a real application.
| Comparison | Workflow builders | Build it yourself | Cenna Applications |
|---|---|---|---|
| Day one | |||
| What you start with | A blank canvas of triggers and steps | An empty repository | A working application — interface, agents, skills |
| Who can use it on day one | The person who built the workflow | No one — it doesn't exist yet | The whole team, each with the right permissions |
| Work that needs judgment | Breaks into brittle if-then branches | Months of agent engineering first | Agents built in, with human approval where you want it |
| Security & data | |||
| Where your data flows | Through the vendor's cloud on every run | Stays in yours — once you've built it all | Stays in your cloud account, always |
| Sign-in and access | Per-seat logins, workflows shared loosely | SSO and roles you build yourself | Your SSO and role-based access, built in |
| System credentials | API keys pasted into the vendor's vault | Managed by you, wired by hand | Scoped grants in your account, revocable in one click |
| Cost control | |||
| Seeing what it costs | A per-task invoice at month end | Whatever metering you build | Live spend by app, task, user, and model |
| Runaway automation | A loop quietly burns through tasks | Your guardrails — if you built them | Budgets, alerts, and hard caps included |
| AI and cloud cost together | Not visible at all | Two dashboards you stitch by hand | One true cost per application |
| Customization | |||
| How far you can go | As far as the connectors allow | Unlimited, at engineering pace | Unlimited — it's your source code |
| The interface your team uses | The vendor's runner UI | Built from scratch | A complete UI your developers can reshape |
| When you hit a wall | File a feature request and wait | Keep building | There is no wall — open the code |
| Governance | |||
| Which AI models run | Whatever the vendor embeds | A policy layer you build | One approved list, enforced everywhere |
| Audit trail | Run logs on their platform | Build it yourself | Every agent run traced and priced, in your account |
| Human approvals | Bolted on, where possible | Custom-built | Built into the workflows — approve from Slack |
| Enterprise scale | |||
| From one team to ten | Shadow workflows multiply per seat | Each team largely starts over | Workspaces per team, one platform under them |
| Releasing changes safely | Edits go straight to production | Pipelines you build and maintain | Staging to production, one-click rollback |
| Who keeps it healthy | The vendor's status page | Your on-call rotation | Cenna runs the platform; every app's health on one screen |
A workflow builder automates a step. Building yourself gets you an application in a year. Cenna gives you the application on day one — running in your cloud, governed from one console, and yours to change.
03Beyond the catalog
More ways to use Cenna
The same platform also modernizes what you already run.
Legacy Application Automation
Put agents in front of the systems that have no API, so the work moves even where the software is old.
RPA Modernization
Replace brittle screen-scraping bots with agents that survive a UI change.
Deploy Your Own App
Already built something? Run it on Cenna and it gets the same cloud, governance, and cost controls.
04Always included
Every application comes with the same guarantees
Runs in your cloud
Your AWS or Google Cloud account. Your data never leaves it.
Skills built in
The everyday jobs arrive already built — and your team can add more without engineering.
Costs you can see
Every model call and cloud dollar metered per app, task, and user.
Code you own
Real source code, customized in the tools your developers already use.
Start with the application your business needs.
Thirty minutes: pick the application closest to your team's work, and we'll walk it end to end — including what customizing it for your business looks like.
Get a DemoBuilt for speed. Engineered for control.