DOaaS — DevOps-as-a-Service

Emotional support for your CI/CD pipeline. A public API at doaas.dev that serves witty, on-brand one-liners for blame, motivation, incidents, standups, and more—designed for terminal greetings, Slack bots, GitHub Actions, and badges.

One API, zero seriousness, infinite DevOps one-liners. Because production is pain, and pain deserves an API.

What Problem Does This Solve?

  • Production is hard. On-call, red pipelines, and “did you try rebooting?” get old. DOaaS is a single API for levity—no meetings, no standup bingo, just one curl.
  • Teams need release valves. Standup icebreakers, blame deflection, status pages, Slack bots—instant mood shift, same endpoint.
  • DevOps doesn’t have to be grim. Less corporate jargon, more wit. Less “oh no,” more “okay, we got this.”

Features

  • RESTful API — /help, /random, and 20+ endpoints (/blame, /motivate, /incident, /excuse, /deploy, /rollback, /lgtm, /standup, /meeting, /policy, /audit, /compliance, /risk, and more).
  • Query parameters — format=json|text|shields and mode=normal|chaos|corporate|security|wholesome|toxic|sarcastic|devops (per-endpoint).
  • Shields.io endpoint badge — Dynamic README badges via format=shields and optional style, label, color, labelColor.
  • Secure-by-default — Cache-Control: no-store, CORS scoped to GET/OPTIONS, dependency audits and CodeQL in CI, documented SECURITY.md and private disclosure.
  • Observability — Cloudflare Workers logs and invocation sampling enabled for production debugging.

Quick Start

# Random (chaos mode)
curl -s "https://doaas.dev/random?mode=chaos&format=text"

# Blame, motivate, and more
curl -s "https://doaas.dev/blame?format=text"
curl -s "https://doaas.dev/motivate?format=text"
curl -s "https://doaas.dev/help"

Live demo: doaas.dev/help · Try random: doaas.dev/random?format=text

What I Learned Building This

  • CI/CD — GitHub Actions for lint, format check, generate/validate endpoints, build, unit tests, stress tests, and E2E; CI even calls the live API for motivation and blame steps. Keeping generated files in sync and failing on drift reinforced pipeline-as-code discipline.
  • API design — Clear URL structure, consistent query params (format, mode), multiple response formats (JSON, text, Shields.io schema), and an OpenAPI schema for docs and tooling.
  • Secure-by-default — No-store caching, minimal CORS, dependency audits in CI, CodeQL and OSSF Scorecard for supply-chain security, and a structured security policy for coordinated disclosure.
  • Cloudflare Worker — Edge deployment with Wrangler, custom domain (doaas.dev), env-based config (e.g. production routes), and observability (logs, sampling). TypeScript with Workers types and Node compat flag.
  • WAF & bot security — Running on Cloudflare means the API sits behind Cloudflare’s WAF and bot mitigation; rate limits and abuse protection are part of the platform, and the README and SECURITY policy set expectations for respectful use and rate limits.
  • Open source rigor — Markdown lint, Prettier, ESLint, Husky + lint-staged, CONTRIBUTING and PR templates, and a changelog so users and contributors know what’s in each release.

Key Differentiators

  • Production-ready — Custom domain, observability, SECURITY.md, and semantic versioning (v1.0.0, v1.1.0).
  • Integrations — INTEGRATIONS.md documents cURL, shell functions, terminal greetings, GitHub Actions, Shields.io badges, and more.
  • OpenSSF Scorecard — Supply-chain security posture visible via the project badge.
  • MIT licensed — Free to use, integrate, and extend.

Documentation & Links