Production Release Process
acty.dev defines a practical production release process for small software and AI workflow projects, delivered as a release checklist, a rollback path, an environment and secrets checklist, a smoke-test plan, and documentation.
We define a practical production release process for small software and AI workflow projects, delivered as a release checklist, a rollback path, an environment and secrets checklist, a smoke-test plan, and documentation. This stays within DevOps-enabled delivery and does not promise incident staffing, uptime targets, or enterprise release governance.
The problem we solve
A team can build features but lacks a predictable way to promote them to production: there is no release checklist, no agreed rollback path, environment and secrets live in someone's head, and there is no smoke test, so each release is a risk.
How we work
- Release review.We review how the project is built, deployed, and promoted today, and the environment and secrets it depends on, then agree on a scoped release process.
- Process definition.We define the release checklist, the rollback path, the environment and secrets checklist, and the smoke-test plan against the agreed scope.
- Test release and smoke check.We run the release process once and the smoke test to confirm the steps and the rollback path work as written.
- Document and hand off.We hand over the release process documentation, and offer ongoing DevOps support when further work is needed.
What you bring / what you get
Inputs
- The application repository and deployment target
- The current build, deploy, and promotion approach
- The environment variables and secrets the project depends on
Outputs
- A release checklist and a rollback path
- An environment and secrets checklist and a smoke-test plan
- Release process documentation
Definition of done.A practical production release process for a small software or AI workflow project, delivered as a release checklist, a rollback path, an environment and secrets checklist, a smoke-test plan, and documentation, so production promotion is predictable instead of improvised.
Fit and anti-fit
Good fit
- Teams that can build features but have no predictable production promotion
- Small software or AI workflow projects without a release checklist or rollback path
Not a fit
- Requests for incident staffing, uptime targets, or enterprise release governance
- Kubernetes, SRE, or large-scale regulated infrastructure requests
Questions
- What does a production release process include?
- A release checklist, a rollback path, an environment and secrets checklist, and a smoke-test plan, delivered with documentation, so a small software or AI workflow project can promote to production predictably.
- What proof supports this service?
- acty.dev follows its own release, preview, and promote discipline on this project as a working internal-project apparatus, which is the basis for this service. It is not presented as third-party enterprise release governance proof.
- What is out of scope?
- We do not promise incident staffing, uptime targets, or enterprise release governance without a separate scope, and we do not make Kubernetes, SRE, or always-on incident response promises.
- What do you need from us to start?
- The application repository and deployment target, your current build, deploy, and promotion approach, and the environment variables and secrets the project depends on.
- How is this priced?
- A scoped release process can start from a few hundred dollars. Larger setup work and ongoing DevOps support are scoped after a task review.
- Is this set up once or ongoing?
- It is delivered as a release process you can repeat, with a checklist, a rollback path, an environment and secrets checklist, and a smoke-test plan, and can also run as recurring work scoped after a task review.
Pricing.A scoped release process can start from a few hundred dollars. Larger setup work and ongoing DevOps support are scoped after a task review. (Scoped after a task review.)
