Tech Lead · WOM Colombia
Deployment platform
The internal platform the whole team ships with: from a push to production with ephemeral environments, managed secrets, a chat bot and an audit trail for every step.
Team chat#deploys
You
/deploy api v1.2 Deploy bot
Signed image in the registrydone
Ephemeral namespace with its own URLdone
Environment smoke testspassed
Production · 2 replicasdeployed
From a push to production
- A push or a commandA deploy starts with a git push, a chat command or the UI. Everything enters through a central API that checks role-based permissions.
- The API queues the workBuilds, rollouts and smoke tests run on async workers coordinated through Redis queues. The UI never blocks waiting.
- Quality in parallelLint, unit, e2e and coverage run at once with per-branch caching. If they pass, an unprivileged OCI image is built and signed in the private registry.
- Ephemeral environmentEach feature deploys to an isolated namespace with its own URL. Secrets are injected encrypted at runtime and smoke tests run against that environment.
- Production on two targetsThe same flow promotes to on-premise Kubernetes and to AWS EKS, with one-click rollback to the previous version.
- Everything is auditedEvery step is written to an immutable log, metrics reach Prometheus and Grafana, and the bot replies in the chat with the result.
Highlights
- 100% of the development team ships daily with the platform.
- One ephemeral environment per feature, with its own URL, created and destroyed automatically.
- Nothing reaches production without passing the ephemeral environment smoke tests.
- One-click rollback to the previous version, with full history.
- Zero secrets in repositories: encrypted runtime injection, masked in every log.
- Deploy from the chat, without opening consoles or dashboards, with role-based permissions.
- One flow, two targets: on-premise and cloud.
