AI, automation and new e-services on infrastructure you control.
Stackship is a cloud platform you install in your own datacenter, in a shared IT service, or with a Swedish hosting partner. Developers and suppliers order databases and runtimes themselves, and service owners can build new services with AI agents in Circuit.
What municipalities ask us about
A safe way to start using AI
Models run on your own hardware, through an agreement you already have, or through our model service. In Circuit, service owners can build and try a service at no cost, and no system goes into operation until a person has classified and approved it.
Automation without a new cloud service for every step
Databases, storage, functions and queues live on the same platform, with the same permissions and the same invoice. A nightly export, an invoice flow or a sync between the HR system and the directory runs next to your other systems, and Circuit can build and maintain them for you.
A faster pace for new e-services
Developers and suppliers order what they need themselves, within the quotas and permissions IT has set. In Circuit, service owners describe the need in their own words and watch the prototype grow in the conversation. That prototype then becomes the system that goes into operation.
Security and procurement
What usually decides whether a platform can be used in a municipality.
Your data stays in your environment
The platform runs in an environment that you or your hosting partner control, and your applications and data never pass through Stackship. Stackship AB is a Swedish company with Swedish owners and is not subject to the CLOUD Act.
AI profiles classified with KLASSA
When the platform itself uses a language model, as the Sentinel operations assistant does, the model is tied to an AI profile classified with KLASSA, the information classification model Swedish municipalities and regions use. The platform sends no data to a model whose profile isn't cleared for its level.
Traceable to the person
Every action is logged with the person's own identity, all the way into the Kubernetes audit log. Permissions can be set on a single database or service.
One license for the whole platform
Databases, functions, storage and the platform's other services are covered by the same license, priced by the capacity you reserve. During the license period the platform sends us no telemetry.
AI with or without your own hardware
You've already bought AI hardware
Install the platform on the same cluster and run the models in GPU instances. Circuit and your own services call them there, no request leaves the building, and we charge nothing for the model.
Fits: municipalities, regions and agencies with GPU servers that aren't yet fully used
You don't have AI hardware
Use an agreement you already have with a model provider, or our model service at a fixed monthly package price. You avoid signing a separate AI agreement, and you can move to your own hardware when the need is there.
Fits: organizations that want to try before investing in hardware
Build e-services and automations with Circuit
Circuit has three steps. In Build, service owners describe a need and the AI agent builds the service in the conversation. In Deploy, the system is classified, its documentation and runbook are written, its cost is worked out and its owners are named. Nothing goes into operation until all of that is in place.
In Operate, the system stays in Circuit, which keeps it patched and up to date. Every change is made in its own conversation and reaches production only once a person has approved it. The code, documentation and decision log live in your own git repository.
Read more about CircuitThree ways to run the platform
You choose who operates the infrastructure. Developers get the same platform in all three cases.
In your own datacenter
The platform is installed on your own Kubernetes. Clusters connect outbound, so you don't need to open the firewall for inbound traffic.
Fits: regions, agencies and larger municipalities with their own operations
In a shared IT service
The shared service organization runs one installation, and each municipality gets its own separate environment with its own users, quotas and network rules. No municipality can see another's resources.
Fits: municipal associations and joint IT boards
With a Swedish hosting partner
A partner runs the platform in Swedish datacenters and you get your own separate environment there. You don't need Kubernetes skills in-house. Which partner meets your jurisdiction requirements is your call.
Fits: smaller municipalities without their own Kubernetes operations
Frequently asked questions
About AI, confidentiality and procurement.
What do you want to get started with?
Tell us about the AI initiative, automation or e-service you have in mind, and we'll go through how it would run on the platform and what stays with you.
Book a walkthrough