What BindDock does

BindDock gives you one place to connect and view the services that support your web stack. Supabase, Vercel, GitHub, and Resend connections are available today. Your infrastructure stays hosted by, owned through, and controlled in the original provider; BindDock does not move projects into BindDock-owned infrastructure.

Create and secure your account

1. Create an account with email and password, or continue with Google or GitHub.
2. Complete email confirmation if your sign-up method asks for it.
3. Sign in to open your protected dashboard.

Keep control of the email account and social account you use to sign in. BindDock support will never ask for your password, provider access token, refresh token, or encryption key.

Connect Supabase

1. Open Connections in the BindDock dashboard.
2. Select Supabase and choose to connect an account.
3. Review the authorization screen. BindDock requests read-only access to organizations and projects.
4. Approve the connection to return to BindDock and select the account you want to view.

You can connect more than one Supabase account. BindDock stores the provider authorization securely and encrypts provider tokens before database storage.

Connect Vercel

1. Open Connections and choose to connect Vercel.
2. In Vercel, choose the personal account or team where you want to install BindDock.
3. Review the requested project access and complete the Vercel installation.
4. Vercel completes the installation. Return to or refresh BindDock to view the projects permitted by it.

Vercel V1 reads project names, identifiers, framework information, and update times. It does not create projects, trigger deployments, or change project settings. You can connect multiple Vercel installations under one BindDock login.

Connect GitHub

1. Open Connections and choose to connect GitHub.
2. Install the BindDock GitHub App for a personal account or organization.
3. Choose access to all repositories or only selected repositories.
4. Return to BindDock to view the repository metadata granted to that installation.

GitHub V1 reads repository names, owners, visibility, default branches, and update times. It does not read file contents, clone repositories, create commits, or perform writes. BindDock generates short-lived installation tokens only when refreshing this metadata and does not store them.

Connect Resend

1. Open Connections and choose to connect Resend.
2. Sign in to Resend, choose the intended workspace, and review the authorization request.
3. Approve the connection to return to BindDock and view the workspace's domains and verification statuses.

Resend currently requires its full_access OAuth scope for domain-listing routes because it does not offer a domain-read-only scope. BindDock V1 uses that grant only to read domains. It does not send email, create, verify, update, or delete domains, write DNS, or create webhooks. You can connect multiple Resend workspaces under one BindDock login.

Disconnect a provider

Use the connection controls in your dashboard to disconnect a provider account. BindDock removes its stored provider connection and associated tokens. For Vercel, BindDock also requests removal of that integration configuration. For GitHub, BindDock requests uninstallation of the GitHub App installation. For Resend, BindDock requests revocation of the OAuth grant. Disconnecting never deletes or modifies provider projects, repositories, domains, or email data.

Need help?

Visit BindDock Support for the public contact address and the information that helps us investigate a problem safely.