Choose your altar, light a candle before your release. Ask the Oracle, cast runes, roll dice. Built for engineering teams who've been through enough.
Ask your question. The Oracle reads the signs and delivers a forecast for your deploy.
Three dice. Ancient numbers carry omens. The sum reveals your fate.
Three runes from the Elder Futhark. Past energy, present state, what comes.
Every engineer knows the feeling: CI is green, staging is perfect — and yet something in your gut says this is going to go wrong. Friday deploys, end-of-quarter releases, that one microservice nobody fully understands — they carry a spiritual weight no unit test can address.
Pray for Deploy is a lighthearted ritual tool for engineering teams. Before you push to prod, light a virtual candle at one of nine sacred altars. Ask the Oracle a question, cast runes, roll dice for omens. The candle burns for one hour. Someone cared enough to pray.
| Altar | Philosophy | Best for |
|---|---|---|
| ✝️ Catholic | Ora et labora — pray and deploy | Anything touching payments |
| ☦️ Orthodox | Господи, помилуй наш деплой | Legacy codebases |
| 🌺 Balinese | Tri Hita Karana — harmony with code | Frontend refactors |
| 🌞 Aztec | Tonatiuh demands your uptime | Database migrations |
| 💀 Voodoo | Baron Samedi watches your logs | Hotfixes at 2am |
| ⛩️ Shinto | The kami of uptime watches over you | Kubernetes rollouts |
| ☸️ Buddhist | Impermanence includes your production | Everything will be fine eventually |
| ⚡ Norse | You sacrificed Friday | Friday deploys |
| 🖥️ Silicon | In logs we trust | The secular engineer |
Pre-performance rituals are well-documented in sports psychology. Athletes who perform consistent routines before competition report lower anxiety and better focus. The same applies to high-stakes software deployments. The act of doing something — even something symbolic — signals to your nervous system that you have committed. The candle is lit. The runes are cast. Now you ship.
When you light a candle, you get a shareable link. Anyone on your team who opens that link sees the same candle burning in their browser — with the same countdown timer. Drop it in your Slack deploy channel: "I lit a candle, who else is praying?" The link encodes the candle data directly in the URL, so no server is needed.
Ask around any engineering org and you'll find a private folklore of deploy rituals, most of them only half-joking. Some teams ring a physical bell mounted near the standup area every time a release goes out clean — and ring it twice, sheepishly, if a hotfix follows within the hour. Others keep a "deploy gnome" or rubber duck that gets passed to whoever is on point for the release, a small object that turns an anxious solo task into something the whole team has eyes on.
The "no Friday deploys" rule is close to universal folklore at this point, but plenty of teams have their own variants: no deploys after 4pm, no deploys the day before a public holiday, no deploys if the release-owner hasn't eaten lunch. None of these are engineering requirements — they're risk-reduction heuristics dressed up as superstition, because admitting "we're tired and more likely to miss something" is a harder sentence to say in standup than "we don't deploy on Fridays."
Incident review culture has its own rituals too. Many SRE teams hold a deliberately blameless retro after any rollback, sometimes literally lighting a candle (the real kind) at the start of the meeting as a signal that the conversation is about the system, not the person who pushed the button. Pray for Deploy borrows that same instinct — distributed teams that can't share a physical candle can still share a link, and the ritual still does its job: it marks the moment, names the risk out loud, and gives everyone permission to be a little nervous together instead of alone.
The Oracle, the dice, and the runes aren't just decorative — each maps to a different way teams talk themselves into shipping. The Oracle is best when someone needs a direct, slightly absurd answer to a specific worry ("will the payment service survive this deploy?") because phrasing the fear as a question already does half the work of naming the risk. The dice are the fastest ritual: three rolls, a number, done — useful for routine deploys where the team mostly wants a 10-second pause button before hitting merge. The runes take the longest to read and produce the most ambiguous result, which makes them oddly well-suited to bigger, riskier releases where the honest answer is "we don't fully know what's going to happen," and a three-part past/present/future reading at least gives the team a shared vocabulary for that uncertainty.