Preview & test environments
Give every change a place to prove itself.
Plan isolated environments for review, debugging and testing. Keep the application structure familiar while giving each environment its own configuration and lifecycle.
- 01 /
Create
An isolated review context
- 02 /
Review
The application and its dependencies
- 03 /
Clean up
Resources no longer needed
Make environment ownership explicit.
Review the whole application
An API change often depends on a worker, a database or a frontend. Define the services needed to exercise the change together.
Use data meant for testing
Choose seeded or sanitised data and environment-specific secrets. A review deployment should not need production credentials to be useful.
Set the end date at the start
Assign an owner and a cleanup rule. Include compute, storage and external resources when deciding what should happen after review.
A few practical questions.
Can I use this for staging as well?
Yes, staging follows the same environment model but usually has a longer lifecycle. Keep its configuration and access separate from production.
Will deleting an environment remove everything?
Confirm the deletion policy for each resource, especially persistent data and services outside the cluster. Your cleanup plan should explicitly cover what is retained.
Keep exploring
See how it fits together.
Build with Kapten
Start with one service.
Build from there.
Tell us what you want to deploy. We review each request and follow up about fit and onboarding on your preferred cloud.
Free during early access. No card required. Cloud usage billed separately.