When someone joins
Their onboarding brief lists every service they now own or watch: the account email, how to sign in, which card bills it, and who to call at the vendor. Day one context that usually lives in a predecessor's head.
Dependency continuity for distributed teams
Every vendor account is owned by someone. Until they leave.
ServiceGuard maps every service your company runs on to a person who owns it. Expiring cards get caught before production notices, new teammates learn their dependencies on day one, and when someone leaves, everything they owned is handed off, not lost.
Services tracked
42 ↑ 4 this quarter
Expiring in 90 days
3 ↑ 1 this month
Unowned
2 ↑ 1 after handoff
Owners bouncing
1 — unchanged
Confirmed this quarter
86% ↑ 2.5%
Needs attention
| Status | Service | Owner | Card on file | Expires | Last confirmed |
|---|---|---|---|---|---|
| expiring | Postmark | Dana Whitfield | Visa ·· 4412 | 09 / 26 | 3 weeks ago |
| bouncing | Datadog | Miriam Okafor | Amex ·· 1004 | 11 / 27 | 7 months ago |
| unowned | Intercom | — | Visa ·· 7730 | 02 / 28 | 4 months ago |
| confirmed | Slack | Priya Raman | Visa ·· 4412 | 04 / 28 | 2 weeks ago |
Tracks the vendors you already pay
- AWS
- Slack
- Notion
- Zoom
- Datadog
- Figma
- QuickBooks
- and anything with a card on file
Someone leaves. Nothing announces what they owned.
The accounts keep working until a card expires, an invoice bounces, or a renewal lands in a deprovisioned inbox. That is how a forgotten subscription becomes a production outage. A stale registry is worse than none: false confidence fails harder than known ignorance.
Onboarding and offboarding
Run it when someone joins or leaves
A registry you have to remember to update is a registry that goes stale. ServiceGuard attaches the writes to moments that already happen, so the map stays current and anyone new, an employee or department leader, can learn who runs on what in minutes.
When someone leaves
Their manager runs the handoff. Every owned account gets a new owner, or is deliberately left unowned and flagged. That is a decision, not an accident. The handoff won't complete while owned services are unassigned.
Outage prevention
An expiry alert that keeps the registry honest
Before a card on file expires, the owner gets an email listing every service billed to that card. It offers exactly three answers, and one of them is the point.
Confirms the new expiry and stamps "last confirmed" for everyone to see.
Honest snoozing beats silent ignoring.
The ownership-decay catch. One click flags the service for reassignment instead of letting it quietly rot.
Alerts arrive by email and, on your schedule, by SMS, which respects each person's working hours. A hard email bounce is treated as its own signal: the owner may be gone.
The core risk
Built to surface its own staleness
- Last confirmed, everywhere Every service shows when a human last vouched for it. Silent staleness becomes visible staleness.
- Bounces are evidence A bouncing owner address means the person is likely deprovisioned. The service gets flagged, not skipped.
- Reviews prompted by evidence Ownership reviews trigger on stale confirmations and bounces, not a calendar reminder everyone ignores.
- Orphans stay visible A service left unowned keeps its place in your cost-center tree, marked amber until someone claims it.
Trust
What we never store
Full card numbers
Last four digits and expiry only: enough to recognize a card, never enough to use one.
Vendor passwords
Access notes record the sign-in method, account email, and vendor contact. Credentials belong in your password manager.
API access to your billing
ServiceGuard never connects to a vendor to change payment methods. You update the card; we deep-link you there and record that you did.
Password-only accounts
Every ServiceGuard sign-in requires an authenticator app. Not SMS codes, not emailed codes. A second factor that stays a second factor.
Find out who owns the accounts
before you need to know
Set up takes an afternoon: pick your vendors from a grid, paste what's on the card, done. Sign up with your work email. If your team already has a workspace, you'll join it.