Let’s talk.
Thirty-minute call. We will scope your workflows, confirm what a deployment inside your Azure tenant looks like, and answer pricing on the same day.
Your data, your tenant
Engine deploys into your own Azure subscription. CivicFlow never holds your form data.
Signed configuration
Every config update is Ed25519-signed by CivicFlow and verified by your Engine before it applies.
Canadian residency
Default region: Azure Canada Central. PIPEDA-aligned out of the box.
What happens next
No sales sequence, no drip campaign. Three steps, and you can stop at any of them.
- Straight away
Your message reaches a person
It goes to the CivicFlow team directly — not a ticket queue, and not an autoresponder that asks you to fill in a second form.
- Within one business day
We reply with a time
A short note with two or three slots, and any question we need answered before the call so the thirty minutes are not spent on setup.
- On the call
Scope, deployment, price
We walk your workflows, show what a deployment inside your own Azure subscription involves, and give you a number the same day.
Asked before every call
Answered here so you do not have to book a meeting to find out.
Where does our data actually live?
Inside your own Azure subscription, in the region you choose — Canada Central by default. Form submissions, files and staff identities never reach CivicFlow. We hold your subscription record and the app configuration, and nothing from inside your workflows.
Do we need to give CivicFlow access to our tenant?
No standing access. Deployment runs from a wizard that you drive, in your own Azure portal, under your own credentials. Your Global Administrator grants a one-time consent for the app itself; nobody at CivicFlow gains rights to change things in your tenant afterwards.
How long does a deployment take?
The infrastructure is provisioned in well under an hour. The part that takes real time is organisational — getting your Global Administrator in a room to approve the consent, which in most municipalities is measured in days rather than minutes.
Can we change an app after we have bought it?
That is the point of the product. Fields, approval steps, emails and roles are edited visually and reach your running deployment within thirty seconds. Your changes are yours alone — they do not affect any other municipality, and no other municipality affects you.
What happens if CivicFlow stops trading?
The software is already running in your subscription, on your infrastructure, holding your data — so it keeps running. Each deployment carries a licence that continues operating without contact, and an emergency licence that activates if we are unreachable for an extended period.
We already have systems we cannot replace. Does that rule us out?
Usually the opposite — most municipalities start with one workflow that nothing currently covers, rather than replacing a finance or records system. Bring the awkward one to the call; it is a better test of fit than the easy one.
Not ready for a call?
Have a look at what is in the marketplace first, or send a short question by email — a one-line answer does not need a meeting.