Tamaat can run as a single-tenant installation in your own cloud account or data centre, on Kubernetes. Everything stays inside your network: the application, your maps and datasets, your published work and your people. We supply the software and support it; you run it.
When to choose it
- Your data must not leave your infrastructure, for a regulation, a contract or a policy.
- Your network is isolated and the platform has to live inside it.
- You already run Kubernetes and want Tamaat operated like the rest of your platform.
- You want to choose when updates are applied.
If you need Canadian hosting without running anything yourself, the hosted service already keeps your data in Canada. See Where Your Data Is Hosted.
How it works
A self-hosted Tamaat is the same software as the hosted service: the web application, the services behind it, a PostgreSQL database and object storage for files and tiles. It is delivered as container images and a Helm chart, with a high-availability configuration that runs several copies of each service and a managed PostgreSQL cluster.
The installation does not need to reach Tamaat to run. It is licensed with a key we issue, which it checks locally. Outbound connections are only the ones you choose: an AI model provider for the assistant, a basemap or geocoding service you connect with your own key, and the open-data sources that coverage studies and satellite monitoring read.
What you need
| Component | Requirement |
|---|---|
| Kubernetes | A conformant cluster, including the managed clusters of the major cloud providers, with an ingress controller |
| Database | PostgreSQL 16 with PostGIS: the bundled cluster, or one you already run |
| Object storage | An S3-compatible bucket: the bundled store, or your own |
| Network | A domain name for the installation and a TLS certificate |
| Identity | Email delivery for invitations and notifications |
| Licence | A licence key from Tamaat for your organization and term |
We size the cluster with you from your seats, data volume and the modules you use. For an evaluation, the same software runs on a single machine.
Who does what
| You | Tamaat | |
|---|---|---|
| Cluster, network and storage | Provide and operate | Advise on sizing |
| Installation | Apply the chart with your values | Provide the chart, the images and a guided first installation |
| Updates | Choose when to apply each release | Provide every release with its notes and upgrade steps |
| Backups | Run and test them | Document what to back up |
| Access and identity | Control who reaches the installation | Build the controls into the product |
| Licence | Keep the key current | Issue and renew it |
| Support | Report problems with the context we ask for | Answer under the agreement's support commitments |
Updates
Each release ships as a chart version with its images and release notes. You apply it in a maintenance window of your choosing, after a database backup, and can roll back to the previous release with one command if something is wrong.
Hosted and self-hosted together
Organizations that run both keep them apart: a self-hosted installation is its own platform, with its own accounts, workspaces and Server. Work moves between them by export and import.