# Run on Cordango: what a live app gains from the platform > A live Cordango app is not an isolated generated application. It joins the company platform: personal views without forking, identity and permissions that stay intact, the same people and organizations as every other app, cross-app work and managed hosting in Germany. Source: https://www.cordango.com/run-on-cordango/ Language: en HOW IT WORKS · 04 # An app becomes part of your company. 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. [Book a demo →](https://www.cordango.com/contact/) [What it inherits →](https://www.cordango.com/run-on-cordango/#personal-views) 1. [01 Idea / Prompt](https://www.cordango.com/generate/) 2. [02 App Definition](https://www.cordango.com/app-definition/) 3. [03 App Contract](https://www.cordango.com/app-contract/) 4. 04 Live Business App 1. [Personal views Same app, different screens](https://www.cordango.com/run-on-cordango/#personal-views) 2. [Governance Users, roles, permissions, audit](https://www.cordango.com/run-on-cordango/#governance) 3. [Shared context People, organizations, teams](https://www.cordango.com/run-on-cordango/#shared-context) 4. [Connected work Other apps, dashboards, agents](https://www.cordango.com/run-on-cordango/#connected-work) 5. [Platform operations Hosting, backups, updates](https://www.cordango.com/run-on-cordango/#operations) FIG.00 — STAGE 04 OF 04 · LIVE BUSINESS APP ## Personal, without becoming fragmented. 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. - YOU Your columns, your layout, your dashboard - ONE One app underneath, not a copy per person - SAFE A personal view never widens what you may see - ROLE A warehouse view and a finance view of the same data [Personal views in depth →](https://www.cordango.com/make-it-yours/) Same app · three people Deliveries \# mara · dispatch board by route · today only · driver + van columns \# tomas · finance table by customer · unbilled first · value + terms \# lena · support list by promised date · late at the top ✔ one app one set of records · one permission model ## Built by a person. Owned by the company. 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. - OWN Company-owned, with a named successor when people move on - AUTH Users, roles and fine-grained permissions, from the platform - LOG One audit trail and one security model across every app - SSO One account to grant and one to revoke, everywhere at once [Security and permissions in depth →](https://www.cordango.com/security/) Roles & permissions Acme Ltd | | Admin | Manager | Member | | --- | --- | --- | --- | | View customers | ✓ | ✓ | ✓ | | Edit invoices | ✓ | ✓ | ✗ | | Manage people | ✓ | ✗ | ✗ | | Install apps | ✓ | ✗ | ✗ | ## Born Contextual. — the same company world Cordango apps do not live in separate business silos. A new app reads the company's own People, Organizations and Teams instead of starting a directory of its own, so the person on a task is the same person whose leave was approved and who owns the deal. Connected means apps can communicate. Contextual means they already understand the same company world. That is what makes the second app cheaper than the first: it arrives knowing who works here, which companies you deal with and who is responsible for what. - PEOPLE One person record, read by every app that mentions them - ORGS One record per company you work with, however many apps touch it - TEAMS Reporting lines and teams the platform already knows - TIME Calendar and files shared across apps, not kept per app [How the company model grows →](https://www.cordango.com/company-graph/) Shared context Lena K. \# one person, four apps Lena K. Person · support team · reports to Mara ✔ helpdesk assignee on 12 open tickets ✔ pto approved leave · 14–18 Oct ✔ projects owner of 3 tasks in Globex onboarding ✔ calendar the same absence, the same tasks \# nobody typed her name twice ## Connected work, not integration work. 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. - ONE Every app lives on one shared data core - LIVE Widgets read live data, not last night's copy - ASK Agents and MCP reach every app under the same permissions - RBAC Everyone sees only what they are allowed to, in every widget [Connected apps and the dashboard →](https://www.cordango.com/dashboard/) Acme Ltd — company dashboard 4 apps · 0 integrations €18.4k OVERDUE · BILLING × CRM 12 OPEN TICKETS · SUPPORT 7 TRIALS ENDING · CRM 3 ON VACATION · HR ## What the platform runs for you. None of this is configured per app. It is the platform, so an app you create on Tuesday already has it. IDENTITY #### One sign-in One account per person across every app. Access granted once, and ended once when they leave. TENANT #### Tenant isolation Your data sits in its own database schema, enforced below the application, not by a WHERE clause. AUDIT #### Field-level history Who changed what, when, on the record itself. You do not model an audit entity to get it. API #### REST and MCP Every app is reachable programmatically, under the same permissions as a person. OPS #### Managed hosting Backups, updates and patching are ours. The person who asked for the app never becomes its administrator. EU #### German hosting Built and hosted in Germany on EU infrastructure, GDPR-first, with one data processing agreement rather than one per tool. REVIEW #### Nothing new to assess 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. PORT #### Portable format The app is a definition. It can be exported, versioned, moved and built into software you own. MORE ## Further reading - [**Personal by design** One app, different ways to work](https://www.cordango.com/make-it-yours/) - [**Governance built in** Identity, permissions and audit included](https://www.cordango.com/security/) - [**Connected by default** Apps work together from day one](https://www.cordango.com/dashboard/) - [**Agents & APIs** Agents, MCP and APIs across your whole company](https://www.cordango.com/ai/) - [**Platform foundation** The company foundation underneath every app](https://www.cordango.com/platform/) - [**Shared context** People and company data stay consistent](https://www.cordango.com/company-graph/) - [**Capabilities** CRM, projects, PTO, support and more](https://www.cordango.com/capabilities/) - [**Sample apps** Explore real apps you can install and make yours](https://www.cordango.com/templates/) NEXT ## Built once. Ready for the company. 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. [Book a demo →](https://www.cordango.com/contact/) [Start at the beginning →](https://www.cordango.com/generate/)