Platform · Governance
Built to outlast the people who built it.
An application your organization depends on can’t depend on any one person. Not the builder who made it, and not us. In Plant an App, who can change what is defined, every change is checked and recorded, and the data, the history, and the right to keep it running stay with you.
Drift
Speed isn’t the risk. Speed without governance is.
It starts as a quick win. Five years later, it runs a public service, and the people who built it have moved on.
- 1
It lives in one person’s head.
The builder knows how it works. When they move on, the knowledge goes with them.
- 2
Changes go straight in.
Someone edits the live system, and no one can say what changed, or why.
- 3
No one knows what depends on what.
A field disappears, and a report three screens away stops working.
- 4
It’s only as safe as its vendor.
If the vendor goes, the system goes with it, and everything built on top.
Fast to build.Safe to depend on.
Assign
Using it and changing it are different jobs.
Not everyone who works in an application can change it. Building is a role, given to named people, and the most powerful tools are kept for the people who run the platform.
People who use it.
Work in the application, within the permissions their roles give them.
Managers.
Manage users and see across the work, without changing how the application is built.
Builders.
Build and change the application, each on a named developer seat.
Engineers and administrators.
See the technical detail behind errors, run the platform’s settings, and decide who gets to build.
Building is licensed per developer, never per person who uses the application.
Check
Mistakes stop at the save.
Broken steps, missing paths, and missing dependencies are caught while the change is made, before it’s saved, and before anyone depends on it.
Can’t save yetWorkflow · Issue permit
- Decision “Fee required?”Has no label for one of its paths
- Task “Send permit”Isn’t connected to the rest of the process
Fix 2 problems to save
Broken workflows can’t be saved.
Disconnected steps, unlabeled decisions, and incomplete actions are flagged, and the save waits until they’re fixed.
Tested with real inputs.
Run a workflow with sample inputs and see what it returns, before anyone depends on it.
Nothing pulled out from under.
An entity can’t be deleted while other entities still depend on it.
The database follows the model.
Schema changes are generated from the data model. No hand-written migration scripts.
Record
Every change has an author, and a way back.
Changes are tracked as builders make them and committed to your own Git repository, so the application’s history is never lost, and never only in someone’s memory.
Tracked as it’s made.
Every change to pages, entities, workflows, APIs, jobs, roles, and settings is tracked: who made it, and when.
Committed with a reason.
Each commit to your own Git repository carries a title, a description, and its author.
Restored when it’s needed.
Bring back an earlier version of any item from its history.
Secrets stay out.
Connector credentials never go into Git. Each environment keeps its own.
The history lives in Git.Not in anyone’s memory.
Standardize
Approved once. Used everywhere.
Governance isn’t only stopping the wrong change. It’s making the right way the easy way, so every builder works with your data and your systems the same way.
Approved implementations.
A Workflow Contract fixes what a step takes and returns, and the implementation behind it is chosen and changed in one place.
Actions your developers publish.
Developers publish approved actions, and every builder uses them instead of writing their own.
Documented as it’s built.
Every saved workflow becomes an action with its inputs, outputs, and description, ready for the next builder.
Continue
If we can’t continue, your system does.
Public services run for decades. Your contract can protect them for that long: with source code escrow, the platform’s source code is held by an independent agent, and released to you if Plant an App can no longer support it.
- 1
Agreed in your contract.
The escrow terms, including when the code is released, are part of the contract you negotiate.
- 2
Held independently.
The platform’s source code is deposited with an independent escrow agent, not kept only by us.
- 3
Released if we can’t continue.
If the agreed conditions are met, such as Plant an App closing or ending support, the agent releases the code to you.
- 4
Your system carries on.
Your team or another partner maintains the platform from its source, under the terms you agreed.
Your data, in your database.
Every record sits in standard SQL Server tables with readable names, usable without Plant an App.
Your application, in your Git.
Its configuration lives in your own repository, under your control.
Your work, defined in the contract.
Rights to the configurations, integrations, and custom code built for you are defined in the contract. Plant an App keeps its commercial product.
Subscription or perpetual.
License by subscription, or perpetually, so your applications keep running whether or not you renew.
Built to outlast the people who built it.Including us.
Related capabilities
Build it fast.Keep it for decades.
Talk to us about the systems your organization depends on, who builds and changes them, and how long they have to last, and see how Plant an App keeps them governed, and yours.