Markdown

Connections and services

Connections

Under Connections you store access to Sentry, Firebase, Cloudflare, IONOS, Kubernetes, and email delivery once for your whole organization.

On this page

Under Connections, administrators store access to external services once for the whole organization; in projects you pick them from a list.

Click Add connection, then choose the tile for the service. The picker is grouped by category (DNS, Email, Push notifications, Error tracking, Cloud); the same grouping applies to connections you already added, so multiple accounts in one category sit side by side. Enter a name and a slug for display in projects, and enter the credentials, which the platform checks right away for several services.

Capturing errors with Sentry

You connect your Sentry account through Connect with Sentry for sentry.io or with an API token, which also covers self-hosted instances. When you enable Sentry for a component under Features, the platform creates the project in your account and writes the DSN into the configuration. Sentry: credentials describes the token, and Error tracking gives the overview.

Push notifications with Firebase

Google / Firebase is used for push notifications in apps; the recommended option is a service account JSON, while Connect with Firebase through OAuth still carries a Beta badge. On the app, enable Firebase under Features and select the connection. Firebase: credentials walks through both options.

DNS records through Cloudflare or IONOS

If your domain is hosted at Cloudflare, you connect the zone with an API token. The platform then writes A and CNAME records itself, as DNS-only without the proxy, so that Let’s Encrypt can reach your server. Set DNS with Cloudflare describes the token.

At IONOS you store an API key from the Hosting Developer Hub (not IONOS Cloud); the platform writes the records into the matching hosting zone. Set DNS with IONOS describes the steps.

Email delivery

Mailtrap needs only an API token and shows status, plan, and sending domains including DNS checks; Email (SMTP) takes a generic account for any other provider. Both appear in projects under Mail account. SMTP with Mailtrap covers the setup, and Email delivery explains the differences.

Kubernetes access

The platform checks the access file of your cluster and keeps it encrypted. Applications still run with Docker on the server today; rolling them out onto the cluster comes next. Store Kubernetes access has more.

What is not under Connections

Access to the App Store, Play Store, and Microsoft Store lives under Store accounts and is selected on the app, as Store accounts describes. SSH access and the API tokens for Hetzner and Hostinger live under Servers behind Manage credentials; Cloud servers shows the procedure.