Deploy badges
Drop a small image into a README or wiki to show when an environment was last deployed and whether it's locked — without exposing anything about your pipeline.
When you’d use this
Open-source READMEs, internal wikis, and status pages are all places where people want to know “what’s the state of this app?” without opening another tool. A pair of small SVG badges answers that — no login, no extra tab, no pipeline details leaking out.
The two badges
- Deploy status — shows when the destination was last deployed and by whom.
- Lock status — shows whether the destination is currently locked.
Both are public by default, so you can use them on hosted open-source projects.
How they’re served
Shipyrd exposes a JSON endpoint per destination that’s compatible with shields.io’s endpoint adapter. Shields.io renders the SVG; Shipyrd provides the live data.
The endpoints follow this pattern:
https://badge.shipyrd.io/applications/<APP_ID>/destinations/<DESTINATION>/badge/deploy.json
https://badge.shipyrd.io/applications/<APP_ID>/destinations/<DESTINATION>/badge/lock.json
You wrap each one with shields.io to get the actual badge image.
Setup
-
Open the application and destination in Shipyrd. Each destination has its badge URLs ready to copy.
-
Paste the markdown into your README:
 Or use the JSON URL directly with any other shields.io-compatible badge renderer.
Related
- More background: Deploy status and lock badges for your app on From The Keyboard
- Deploy locks — what the lock badge reflects
- Notifications — for richer status pushed into Slack or a webhook