Project Provisioning

A request for a new environment, from a form, a ticket, or an approved intake, prompts a Beam agent to read your naming and region conventions and stand up a Supabase project through the Management API where your keys allow. It records the project reference back on the originating ticket and notifies the requester. A request that names an unusual region, exceeds the organization's project quota, or lacks an approver on record is held and routed to an engineer, so a person confirms the setup before anything is created instead of the agent guessing at intent.

Usage and Quota Watch

On a schedule, the agent reads each Supabase project's usage figures the API exposes: database size, bandwidth, and active connections against the plan. Following your thresholds, it updates a status record and posts an early warning to the owning team when a project trends toward a limit. A project already over a hard cap, or one whose growth looks abnormal rather than expected, is escalated to an engineer with the numbers, so a human decides whether to upgrade the plan, prune data, or investigate the spike before service degrades.

Access and Key Review

When membership or API keys change, the agent reads the organization's members and service roles the Management API returns and compares them to your approved access list. Entries that match policy are noted as reviewed; a member who no longer belongs, or a key past its rotation date, is flagged. It updates the audit record and notifies the owner, but never removes access itself: revocation and role changes are routed to an administrator with the discrepancy spelled out, so a person makes the security call rather than an automatic sweep.