Operate
Hosting and operations
Where and how Konstrukt is hosted and operated — Swedish hosting and sub-processors, tenant isolation, encryption, backup and restore, availability, release tracks and how releases are announced.
This page describes how the Konstrukt service is hosted and operated. The legal commitments are in the general terms and the sub-processor list on konstrukt.se. Those pages take precedence over this one.
Hosting and data location#
Konstrukt runs in its own hosting environment, operated with Swedish partners in data centres in Sweden. All processing within the platform takes place in Sweden.
| Sub-processor | Role |
|---|---|
| Nordlo Elevate AB | Operations and hosting: the established hosting environment (through 2026) and the SQL cluster (from 2026) |
| Safespring AB | Operations and hosting infrastructure: the new hosting environment (from 2026) |
| Berget AI AB | AI functionality in the service (from 2026) |
The sub-processor list ↗ is the authoritative and current list. It also covers the tools used when Konstrukt delivers consulting and support. How AI features and the MCP server handle customer data is described on AI and your data ↗; see also AI agents and MCP.
Tenant isolation#
- Each tenant has its own database. Plan data, model, history, users and configuration are stored per tenant.
- Backend services are shared between tenants. They are stateless apart from caching, and every request runs against the calling tenant's database.
- Each tenant has its own host name (
https://{tenant}.konstrukt.app), and its APIs, SQL views and MCP server serve only that tenant.
Encryption#
In the current hosting environment, all data is encrypted in transit and at rest.
Backup and restore#
Backups are stored both on site and off site.
| Backup | Frequency | Retention |
|---|---|---|
| Transaction log backup | Every hour | — |
| Full backup | Every hour | 2 days |
| Daily backup | Every day | 7 days |
| Weekly backup | Every week | 4 weeks |
A customer can ask Konstrukt to restore a tenant from a full backup.
Backups are separate from the platform's own history. History lets users read any earlier state of the data inside the product, without a restore.
Availability#
The availability commitment, how it is measured and the service credits are set out in the general terms ↗.
Releases#
New versions are rolled out in release tracks. Each tenant follows one track.
| Track | Used for |
|---|---|
| Alpha | Development, demo and internal environments; part of quality assurance |
| Beta | Further internal environments, and customers who want early access to new functionality |
| Feature | Most customers |
| Stable | Customers who are particularly sensitive to defects |
- Releases are deployed without advance notice. Maintenance windows can occur, but are not scheduled on a regular basis. The general terms set the limits for planned maintenance.
- After a release, administrators are notified in the interface. The release notes are available from the Help menu, see Tenant administration.
- The version a tenant runs is shown in the Help menu.
Data retention in the platform#
- Plan data is kept until it is deleted.
- History is currently kept until further notice. No specific retention period is guaranteed. Limits on history may be introduced for storage reasons, and may in future depend on the licence.
- Removing history is possible in two ways:
- Empty a value type and change its dimensions. The value type's table is rebuilt without history. See Changing a value type's dimensions.
- Copy the plan, which copies everything except the history tables, then archive and delete the old plan. This removes the history of the whole plan, and point-in-time references in the copy become empty. See Tenant administration.
- Import logs and archived import files are currently kept without automatic purging.
- Backups follow the retention periods above. The general terms state how long personal data may remain in backups after deletion.