Integrations

How integrations work

By default Spaceboy manages everything for you: project repositories live in Spaceboy's GitHub organization, environments are provisioned in Spaceboy's cloud, and agent runs use Spaceboy's Cursor account. Integrations let you swap any of those for services you own — connect once at the organization level and it takes effect immediately: your first connection for a provider becomes the organization-wide default. Anything created after that uses your account; anything created before keeps what it was provisioned with.

Two ideas drive the model. A connection is a credential you've granted Spaceboy — a GitHub App installation on your org, access to a Google Cloud project, or a Cursor API key. You can hold several connections per provider (for example separate dev and prod Google Cloud projects). Routing decides where each connection is used: as the organization-wide default, or overridden per project, and split by development versus production where that matters.

• GitHub — new project repositories are created in your organization.
• Google Cloud — deployed environments (hosting, database, secrets) live in your GCP projects.
• Cursor — workspace agent runs use your Cursor API key.
• Shopify — theme projects preview against your real storefront.
• Apple — connect App Store Connect so iOS builds upload to TestFlight.
• OpenAI — deployed AI apps run on your own OpenAI key instead of Spaceboy's keyless AI gateway.
• Intuit QuickBooks — apps with accounting features run on live QuickBooks Online data through your Intuit developer app.
• Slack — your team chats with a project's agent straight from Slack.

Plan requirements

Bring-your-own platform integrations — GitHub, Google Cloud, and Cursor — are included with the Team plan and above. App credential integrations (Stripe, OpenAI, Intuit QuickBooks, Google sign-in, Apple) are available from the Starter plan up. Anything you don't connect keeps working on Spaceboy's managed defaults, on every plan.

Managing connections

Open Integrations from the sidebar. Each provider card shows its connections with a live status: connected, pending verification, or needs attention. Only organization owners and admins can connect, route, or disconnect. Secrets are stored server-side in an encrypted secret store and are never shown again after you add them.

Disconnecting stops new provisioning from using that connection. Environments and repositories that already exist keep working — the connection in use is pinned when a resource is first provisioned, so nothing already deployed silently moves between clouds.