SECTOR · PUBLIC SECTOR

Automation that can stay inside your own walls

Flomation runs where you need it to run: on your own infrastructure, in your own network, with the data never handed to somebody else. Connect the registers and systems you already use, and put the manual steps between them into a flow.

Start free Talk it through

Deployment: Self-hosted, or UK cloud
Built in: Companies House, DVSA, Police, ONS and more
Forms: Accessible, bilingual, embeddable

Doing more, with the same people

The demand keeps rising, the systems keep multiplying, and the joining up between them is still done by a person with a spreadsheet open.

A service is judged on how it feels to the resident, not on how many systems sit behind it.
Data cannot simply be handed to a third party, so cloud-only tools are ruled out before anyone evaluates them.
The legacy system is not going anywhere, and it rarely has a modern API.
Procurement rewards tools that are cheap to try, and easy to stop using.
Welsh language duties, accessibility regulations and audit expectations apply to everything you publish.

Built for the constraints, not in spite of them

Flomation was designed to be self-hosted from the first release, because for a lot of public bodies that is the only version that can be used at all.

Runs in your environment

Every component can be self-hosted. The runner executes inside your network, reaches your internal systems directly, and the data stays where it already is.

Public data, already wired in

Companies House, DVSA, the Police API, Food Standards, the Environment Agency, ONS, Parliament, postcodes and bank holidays are built-in actions, not integrations you have to write.

Forms that meet the bar

Multi-page forms with conditional questions, file uploads, payment and a language switcher, publishable on their own URL or embedded in your existing site.

Where teams usually start

One process, running end to end, before anything else is touched.

01Permits, licences and applicationsTake the application and the fee in one form, run the eligibility checks automatically, and put an officer in the loop only for the judgement.
02Correspondence and request triageClassify what arrives, route it to the team that owns it, acknowledge it immediately and track the clock against the deadline.
03Supplier and grant checksQuery the public registers for status, officers, control and insolvency history, apply your own rules, and attach the evidence to the approval.
04Self-service for staffLet people request the machine, the access or the account they need, inside guardrails you set, without a ticket and a wait.

The questions your governance team will ask

Worth having the answers to hand before the first conversation.

Every component can run on your own infrastructure, including the runner that executes the work.
Secrets are held per environment, encrypted, and resolved only at the moment a flow runs.
Every execution is recorded with its inputs, its outputs, and who or what started it.
Role-based access control governs who can see and run what, per organisation and environment.

See it built

Worked examples, with the flow and the outcome laid out end to end.

Public Sector ITLet staff manage their own machines, not the IT queueRead the example Local GovernmentRun permits, notices and appeals without the paper chaseRead the example EngineeringOne page for what shipped, and the release note for what is nextRead the example ProcurementCheck a supplier properly, before you onboard themRead the example

Start with one process

Pick the one that generates the most email, build it in an afternoon, and keep it running in your own environment. Add the next when the first has stopped needing you.

Get started