Audit logs

Every meaningful action is recorded with a timestamp, actor and source IP for compliance and debugging.

Your activity

bash
GET /v1/account/logs?limit=100
→ { "logs": [
  { "action": "server.create", "target": "f3c1…", "meta": { "name": "smp" }, "ip": "203.0.113.4", "created_at": "…" },
  { "action": "billing.topup", "meta": { "creditCents": 2500 }, "created_at": "…" }
] }

Recorded actions

server.create, server.delete, server.power, server.suspend
key.create, key.revoke
billing.checkout, billing.topup
budget.update

Platform-wide (admin)

Admins can read activity across every account at GET /v1/admin/logs — useful for incident review and abuse monitoring. Each entry includes the acting account and IP.

Retention

Logs are stored in your Supabase database; retention is whatever you configure there. Logging is best-effort and never blocks the action it describes.