The generated app is only half of what you get. When it runs on Cordango it joins the platform your company already has: the people, the permissions, the audit trail, the other apps and the hosting. Nothing about that is configured per app. It is what running here means.
FIG.00 — STAGE 04 OF 04 · LIVE BUSINESS APP
The usual trade is between one rigid screen everybody resents and a copy of the app per team. The first pushes people into private spreadsheets. The second gives you three versions of the truth and nobody sure which is current.
Cordango takes neither. Shaping your view does not copy the app, fork the process or create a second source of truth. A view describes layout, which columns, which grouping, which filters. It is not a permission and it cannot become one, so sharing a view with a colleague shows them your layout on their own records.
Nobody sets up servers or wires permissions. Every app runs on the same foundation: single sign-on, roles and permissions, a real people directory and one audit trail. Rights are checked underneath every app, on every read and every write, not implemented per app by whoever built it.
The important part is ownership. The app belongs to the company, so it does not leave when the person who made it does. It sits in the company tenant with a named owner and a successor, its users come from the directory, and its audit trail did not live in an account that just got closed.
| Admin | Manager | Member | |
|---|---|---|---|
| View customers | ✓ | ✓ | ✓ |
| Edit invoices | ✓ | ✓ | ✗ |
| Manage people | ✓ | ✗ | ✗ |
| Install apps | ✓ | ✗ | ✗ |
In a normal stack, one dashboard across five tools is an integration project: API keys, connectors, sync jobs, a BI tool and someone to keep it all alive. On Cordango every app is born on the same data core with the same permission model. A widget that spans apps is a view on data that is already in one place.
The same goes for the assistant. Because the apps share records and permissions, it can answer a question that crosses them, which trial customers have an overdue invoice, without anybody wiring three products together first.
None of this is configured per app. It is the platform, so an app you create on Tuesday already has it.
One account per person across every app. Access granted once, and ended once when they leave.
Your data sits in its own database schema, enforced below the application, not by a WHERE clause.
Who changed what, when, on the record itself. You do not model an audit entity to get it.
Every app is reachable programmatically, under the same permissions as a person.
Backups, updates and patching are ours. The person who asked for the app never becomes its administrator.
Built and hosted in Germany on EU infrastructure, GDPR-first, with one data processing agreement rather than one per tool.
A new app is the same platform it was last month. Security review has one system to look at, not a growing list of small tools.
The app is a definition. It can be exported, versioned, moved and built into software you own.
Bring a process that annoys everyone and we turn it into a working app in the demo. About 30 minutes, on a real company platform, with your permissions and your people in it.