Platform Overview
Bloom Cloud is the dashboard behind bloom deploy—organizations, projects, apps, builds, releases, and every piece of infrastructure OTA patching depends on.
Organization Hierarchy
Every resource in Bloom Cloud is scoped under a three-level hierarchy so teams, clients, and product lines stay cleanly isolated:
Organization
The billing and membership boundary. Owns projects, seats, and a subscription plan.
Project
Groups related apps—typically one product, one repository family.
App
A single Flutter app—the unit builds, releases, environments, and secrets attach to.
Linking a Project
Link a local Bloom project to a Cloud app once, and every subsequent bloom deploy targets it automatically:
Role-Based Access Control
Roles are assigned per organization member and gate sensitive actions across every app in that org:
Owner
Full control, including billing, org deletion, and member removal.
Admin
Manage projects, apps, environments, and team membership. No billing or org deletion.
Release Manager
Approve/reject releases, trigger deployments and rollbacks. Cannot touch secrets or signing.
Developer
Trigger builds, view logs and releases. Cannot approve releases or manage secrets/signing.
Audit Log
Builds, release approvals, secret rotations, signing identity changes, and rollbacks are all written to a per-organization audit trail, filterable by actor, resource, and date range from the /audit-log screen in the dashboard.
Audit entries are immutable and retained for the lifetime of the organization—they cannot be edited or deleted by any role, including Owner.