Stackpane Stackpane
Download

Connection Management

Add, edit, and remove project connections with support for Firebase, Supabase, and AWS.

Overview

Connection Management is how you configure Stackpane to access your cloud backends. Each connection stores the provider type, project identifiers, authentication credentials, and environment settings. You can manage multiple connections across Firebase, Supabase, and AWS simultaneously.

Adding a Connection

  1. Open the Connection Editor from the sidebar project picker or the + button.
  2. Enter a connection name — a human-readable label (e.g., “My App - Production”).
  3. Select a provider: Firebase, Supabase, or AWS.
  4. Configure the provider-specific settings (see below).
  5. Click Save.

Firebase

  • Project ID — your Firebase project identifier (from the Firebase Console)
  • Environment — Production or Emulator
  • Auth method (production) — Google Sign-In or Service Account
  • Emulator config (emulator) — host, ports, and launch method

Supabase

  • Project URL — your Supabase project URL (e.g., https://your-ref.supabase.co or http://localhost:54321 for local dev)
  • API key — anon key for client-level access or service role key for admin access

AWS

  • Access Key ID and Secret Access Key — IAM credentials from the AWS Console
  • Region — the AWS region where your resources are located
  • Custom endpoint — optional, for LocalStack or other AWS-compatible services (e.g., http://localhost:4566)

Environment Types

Production

Production connections access your live cloud project:

  • Requires authentication credentials appropriate for the provider
  • All operations affect real data
  • Use with caution for destructive operations

Local Development

Local dev connections access locally running services:

  • Firebase Emulator — no authentication required; configure host and ports for each emulator service; optionally configure a launch method to start/stop the emulator from Stackpane
  • Supabase Docker — uses the local project URL and keys output by supabase start
  • AWS LocalStack — uses a custom endpoint pointing to the LocalStack container; accepts arbitrary credentials

Local connections are safe for testing and development without affecting production data.

Authentication Details

Firebase: Google Sign-In

  1. Select Google Sign-In in the connection editor.
  2. Click Sign in with Google.
  3. Complete the OAuth flow in your browser.
  4. Credentials are stored securely in the macOS Keychain.

Your Google account must have IAM permissions for the Firebase project (Editor, Viewer, or custom roles).

Firebase: Service Account

  1. Select Service Account in the connection editor.
  2. Click Choose File and select the JSON key file.
  3. Stackpane reads and securely stores the credentials in the Keychain.

Service accounts are best for consistent, user-independent access and automated workflows.

Supabase: API Key

  1. Enter the Project URL.
  2. Paste the anon key or service role key from the Supabase Dashboard (Settings > API).
  3. The key is stored securely in the macOS Keychain.

Use the anon key to test with Row-Level Security enabled. Use the service role key for full admin access.

AWS: Access Keys

  1. Enter the Access Key ID and Secret Access Key from the IAM Console.
  2. Select the AWS region.
  3. Credentials are stored securely in the macOS Keychain.

The IAM user or role must have permissions for the services you plan to access (DynamoDB, S3, Cognito).

Editing a Connection

  1. Click the gear icon next to a connection name in the sidebar.
  2. Modify any connection settings.
  3. Click Save to apply changes.

Changes take effect immediately. Stackpane reconnects with the updated settings.

Removing a Connection

  1. Click the gear icon to open the connection editor.
  2. Click Delete Connection.
  3. Confirm the deletion.

Removing a connection also removes its associated bookmarks and pinned items. Credentials are removed from the Keychain.

Switching Connections

Click the project picker in the sidebar to see all saved connections. Click a connection to switch to it. The active connection is highlighted with a checkmark.

When you switch connections:

  • The sidebar updates to show the new project’s data (collections, tables, buckets, or services)
  • Bookmarks and pinned items update to the new connection’s data
  • Any open tabs are closed
  • The interface adapts to the provider type of the new connection

Organizing Connections

You can manage connections for multiple providers side by side. A typical setup might include:

  • Firebase Production — Google Sign-In for safe browsing of live Firestore data
  • Firebase Emulator — local development and testing
  • Supabase Production — service role key for admin access to PostgreSQL
  • Supabase Local — Docker-based local environment
  • AWS Production — IAM credentials for DynamoDB and S3
  • AWS LocalStack — local testing with emulated AWS services

Access common connection actions from the macOS menu bar:

  • Switch between saved connections
  • Open the connection editor
  • View connection status

Tips

  • Use clear naming conventions like “Provider - ProjectName - Environment” to distinguish connections
  • Keep separate connections for production and local dev even for the same project
  • Use Google Sign-In (Firebase) or anon keys (Supabase) for interactive development; use service accounts or service role keys for admin tasks
  • The Keychain securely stores all credentials — never store credentials in plain text files
  • When working across providers, the sidebar clearly indicates which provider and project are active