For teams that need their data inside their own network.
Whether it's a security standard, a procurement policy, a regulator's requirement or simply how your organisation runs its systems — you choose where TerraFlow runs.
Hosted or on-premises
Both run the same TerraFlow. The difference is who runs the system and where the data sits.
| Hosted TerraFlow | TerraFlow Enterprise (on-premises) | |
|---|---|---|
| Where the data lives | TerraFlow-managed infrastructure | Your network only |
| Time to go live | Days | A scoped deployment project |
| Updates | Continuous, applied by us | Released to you, applied by your team |
| Who runs it | We do | Your administrators |
| Backup and disaster recovery | Ours | Yours |
| Support | We can see the system | Diagnostic bundles you generate and send |
| Licensing | Subscription | Perpetual platform licence, annual user seats, annual maintenance |
If speed and a hands-off operation matter most, hosted is the quicker route. If keeping everything inside your own network matters most, read on.
The same system, on your infrastructure
Your servers
Your database
Your field devices sync to you
A platform you own
Support without access
Same workflow, same exports
Unlimited read-only access, included
Viewers are unlimited and free. No cap, no ratio to paid seats, nothing to count.
A Viewer can open the map, search, navigate, print and export. A Viewer cannot capture, edit, change attributes or administer.
On an internal deployment, the people who need to look at locate records far outnumber the people who create them — GIS, engineering, compliance, operations, legal. Charging per pair of eyes on a system you already own would be an argument nobody should have to have.
Fully isolated networks
For networks with no external connection at all — defence, nuclear, federal and critical-infrastructure sites where nothing crosses the boundary in either direction.
Fully isolated deployments are supported on a programme basis, scoped per site. If your network has no external connection, start the conversation early — the packaging and delivery method are part of the engagement rather than a download.
What to know before you sign
There is no copy on our side. No shadow instance, no backup, no analytics feed. Your backup and disaster recovery are yours; make sure someone owns that before you sign.
Support commitments are response commitments. The clock starts when a complete diagnostic bundle arrives. We'd rather publish a number we beat than one we miss.
What a deployment involves
- Scoping. We agree the configuration, the number of users and instances, and which TerraFlow products you're deploying.
- Infrastructure review. Your team and ours agree the server specification, the SQL Server version, the network topology and how field devices will reach the server.
- Deployment and enablement. We install, configure to your data model, migrate what needs migrating, and train your administrators. This is a scoped engagement with a fixed fee, not a download.
- Handover. Your administrators run the system. We hold no access to it.
- Maintenance and support. Annual, from signature, covering releases, patches and support against the current supported version.
Frequently asked questions
Can TerraFlow run entirely on our own servers?
Yes. TerraFlow Enterprise is the on-premises edition — the application, the SQL Server database and all field synchronisation run inside your network. No data replicates to TerraFlow. More on Data Engine.
Do we need a regulatory or policy reason to buy on-premises?
No. On-premises is a deployment choice. If you want TerraFlow on your own infrastructure, we'll scope it with you.
Do we own the licences or rent them?
The platform is yours: it is licensed perpetually for each production instance. Collector and Editor seats are licensed annually. Viewers are unlimited and free. Annual maintenance covers platform releases, patches and support. Fully isolated deployments are licensed annually per site.
What happens if we stop paying maintenance?
The platform keeps running at the installed version. You stop receiving new releases, patches and support until maintenance is reinstated. Collector and Editor seats are annual, so those users need current seat licences to sign in.
Can you support a network you can't reach?
Yes, and it's the reason the support model is built around diagnostic bundles rather than remote sessions. We hold no route into your environment at any point — that's a design decision, not a limitation we work around.
Can we run separate instances in different regions, replicating to a central one?
Yes, as a custom project. Most regional structures are handled on a single instance through roles and data permissions. Where regions need their own replicated instances, we scope and price that work for your deployment.
Is source code escrow available?
Yes, through an independent escrow agent, as a priced annual item.
How do we decide between hosted and on-premises?
Hosted is faster to stand up, updated continuously and run by us. On-premises keeps every record inside your network and puts operation, backups and upgrades with your team. Pick the one whose trade-offs suit how your organisation runs its systems.
Can pipeline operators and locate service providers deploy on-premises?
Yes. One thing to plan for: an on-premises instance holds the records your own users and contractors submit to it. Contractors who also work for other TerraFlow customers will submit to each environment separately.