Stackship documentation 0.7.99
- App Service
Run web applications and APIs built from your repository or from a container image, each with its own hostname, scaling and deployment history.
- Blueprints
What a blueprint is, where the catalog comes from, and what deploying one creates in your resource group.
- Boundaries
A boundary is an isolated environment that holds resource groups, decides who has access to them and keeps its workloads apart from everyone else's.
- Container instances
Run prebuilt container images as a managed service — one or more components, each its own pod, reachable from outside only through the endpoints you add.
- PostgreSQL
Managed PostgreSQL clusters run by the CloudNativePG operator — instances, storage, compute plans, connections, backups and the Data Explorer.
- Vector stores (Qdrant)
Run a Qdrant vector database in a resource group for embeddings and similarity search, and understand how it is secured, exposed and kept.
- SQL Server
Run Microsoft SQL Server as a managed instance — one server with its own database, storage and backups, reachable from the workloads in your boundary.
- Valkey
Key-value stores run Valkey as an in-memory cache — fast, sized by a compute plan, and empty again after every stop or restart.
- Docs
- Functions
Run small pieces of code on an HTTP request or on a schedule, grouped in function namespaces that give them a hostname, shared settings and one identity.
- Jobs
Run a container image once, until it exits — a migration, an import, a report — and read its output.
- Stackship platform
What Stackship is, the concepts everything else builds on — boundaries, resource groups, resources and roles — and where to start.
- Lifecycle Manager
How the platform knows which version of each of its parts runs, where new versions come from, and how an upgrade is planned, checked, rolled out and finished.
- Managed identities
The identity the platform gives each app, function namespace and container instance, so a workload can sign in without holding a credential.
- Monitoring
What the platform measures about your resources, where you see it, and how alerts tell you that something needs attention.
- Policies
Rules a boundary sets for what may run in it — which compute plans, labels, image registries and image tags its workloads may use.
- Portal
How the portal is laid out — header, sidebar, boundary switcher and documentation panel — and where to find things.
- Access control
How the platform decides who may do what — principals, roles, scopes, deny assignments and just-in-time access.
- Container registry
The platform's own container registry — what it stores, who can reach it, how long images are kept, and how it differs from a private registry you connect.
- Resource groups
A resource group is the container every resource lives in. It belongs to one boundary, becomes a namespace on the boundary's clusters, and is a unit of access and of deletion.
- S3 storage
Store files as objects in S3-compatible storage accounts, each with its own server, volume and HTTPS endpoint.
- Secrets
Keep credentials in vaults and hand them to workloads without putting them in configuration.
- Sentinel
Sentinel watches the workloads in your boundary, explains in plain language what is wrong with them, and tells you what to do about it.
- Static Web Apps
Serve a directory of a Git repository over HTTPS exactly as it is committed, with no build step and no server code.