DevOps

The practice of merging development and operations: automated pipelines, shared ownership and infrastructure as code from commit to production.

DevOps is what happens when the people who write software also own how it runs. In practice: every commit flows through automated tests into a deploy pipeline; infrastructure is defined in code and versioned like the app; monitoring and alerting are part of the definition of done. The term blends development and operations, and for a small team it mostly means making shipping boring and reversible.

Why it matters to an indie builder: you are the operations department, so every manual step in your deploy is a step you will someday skip under pressure. A pipeline that runs tests, builds, deploys and rolls back on failure converts release night from a ritual into a non-event. The entire toolchain is free at indie scale: GitHub Actions for CI, a PaaS for deploys, Sentry for errors.

A concrete example: a solo SaaS on Friday afternoon. Before pipelines: deploy meant SSH, git pull, manual migrations, prayer; errors surfaced via customer email, recovery meant more SSH. After an afternoon of setup: push to main triggers tests, a build, database migrations, a deploy to the PaaS, and an automatic rollback if health checks fail. Errors page through Sentry before customers notice. Total cost: the afternoon, once. Every subsequent Friday is free.

Common mistakes: deploying untested code straight to production because the pipeline feels slow (make the pipeline fast instead; a slow pipeline gets bypassed and then deleted), no rollback path, which turns every incident into debugging under fire instead of a revert, secrets committed to the repo (use the CI secret store; scan for leaks), and dashboards nobody reads: alert on what pages a human, and cut alerts that never matter. The devops-adjacent categories on IndieBoot, from CI to hosting to error tracking, exist to be assembled into exactly this loop.