Your cloud account
The server runs in your project, account or subscription, under your network rules. Your developers' collectors post to your address over https, so nothing leaves your network.
For enterprises that need the data inside their own network, we set up Workboard in your cloud account with the cloud's managed PostgreSQL and your identity provider. We are building the self-hosted package now and set up each install together with the customer. Talk to us about your environment and timeline.
The server runs in your project, account or subscription, under your network rules. Your developers' collectors post to your address over https, so nothing leaves your network.
The store runs on your cloud's managed PostgreSQL, so backups, encryption and access follow the policies you already have.
People sign in to the page through your identity provider, with its groups mapped to Workboard roles.
The setup we plan per cloud. Each install uses the cloud's own identity for services, with no long-lived keys.
| Cloud | Runs on | Database | Service identity and secrets |
|---|---|---|---|
| Google Cloud | Cloud Run or GKE | Cloud SQL for PostgreSQL or AlloyDB | Workload Identity |
| AWS | ECS on Fargate | RDS or Aurora PostgreSQL | IAM roles for tasks, Secrets Manager |
| Microsoft Azure | Container Apps | Azure Database for PostgreSQL Flexible Server | Managed identity, Key Vault |
Cognitivi's forward deployed engineer uses Workboard every day on their own Claude Code work, then sits with your team to put it in place.
Today that engineer is Roman Kagan, who leads Cognitivi.
Tell us how many developers use Claude Code and where you would run Workboard. A person at Cognitivi reads every message and replies.