Infrastructure
Infrastructure is now a status page for shared operator dependencies such as SMTP, push, OAuth, encryption, and backup. It is not a federation peer manager.
/infrastructureOverview#
Use this page to answer a simple question: which supporting services are managed for me, configured locally, or still missing?
On Cloud, most cards should show managed. On self-hosted installs, the same cards help you verify whether your local environment is wired correctly and which env-backed services still need setup.
Prerequisites#
- A working capability profile so ClawButler can read deployment mode and infrastructure status
- For self-hosted setups, access to the environment or secret store used by your deployment
Expected Results#
The page should give you:
- -A summary banner that changes depending on Cloud versus self-hosted mode
- -Service cards for SMTP, push APNS, push FCM, push VAPID, OAuth, encryption, and backup
- -Configuration hints on self-hosted installs when a service is still not configured
Web Operations#
Treat the page as a readiness board for support services around the control plane.
Summary Banner
The banner tells you whether infrastructure is managed by the hosted environment or whether your self-hosted deployment still has configuration gaps. This is the fastest top-level check.
Service Cards
Each card is keyed to one backend dependency. Read the status badge first, then use the description and env hint to decide whether you need to configure anything locally.
Cloud vs Self-Hosted
Cloud typically reports managed services. Self-hosted distinguishes configured from not_configured so you can make the page part of deployment verification and incident review.
CLI Operations#
CLI exposes the same capability-derived infrastructure profile:
$ ap infrastructure status