Tunnel Configuration Management
Save tunnel configurations once, reuse them across your team. Flexible scoping, multiple authentication methods, and multi-service routing.
Tunnel Config: "Frontend Dev"
├── Subdomain: frontend.tunnel.asd.host
├── Scope: Team (Frontend Team)
├── Auth: Supabase (JWT validation)
├── Routes
│ ├── / → localhost:3000 (Next.js)
│ ├── /api/* → localhost:8080 (API)
│ └── /ws → localhost:3001 (WebSocket)
├── Keys: 3 active, 1 expired
└── Status: ActiveCapabilities
Saved Tunnel Configurations
Define tunnel configs once, reuse everywhere. Store subdomain, protocols, and authentication settings as reusable configurations.
Flexible Scoping
Scope configs to individual users, teams, departments, or the entire organization. Control who can use which tunnel configurations.
Multiple Auth Methods
Protect tunnels with Basic Auth, OIDC, or Supabase Auth. Configure required claims and audiences for fine-grained access control.
Protocol Support
Full support for HTTP, HTTPS, TCP, and WebSocket protocols. Route multiple services through a single subdomain.
Tunnel Keys
Generate cryptographic keys for tunnel authentication. Keys can be active, revoked, or expired with automatic cleanup.
Multi-Service Routing
Route different paths to different local services. Perfect for microservices and multi-container development environments.
Configuration Scoping
Control who can use tunnel configurations with flexible scope levels. Scoping integrates with your organization hierarchy.
User Scope
Only the config creator can use this tunnel configuration
Team Scope
All members of the assigned team can use this configuration
Department Scope
All teams within a department have access to this config
Organization Scope
Anyone in the organization can use this tunnel configuration
Authentication Methods
Protect your tunnel endpoints with the authentication method that fits your workflow.
| Method | Description | Best For |
|---|---|---|
| None | No authentication required. Tunnel endpoints are publicly accessible. | Public demos, development previews |
| Basic Auth | HTTP Basic Authentication with username and password. | Simple access control, internal tools |
| OIDC | OpenID Connect authentication with any compliant provider. | Enterprise SSO, third-party auth |
| Supabase Auth | Validate Supabase JWTs with audience and claims checking. | Supabase-based applications |
Use Cases
Development Teams
- Share configs across frontend and backend teams
- Consistent tunnel settings for all developers
- Team-scoped configs for project isolation
- Quick onboarding for new team members
CI/CD Pipelines
- Stored configs for automated deployments
- API-driven tunnel creation
- Consistent routing across environments
- Ephemeral tunnels with predefined settings
Client Demos
- Auth-protected demo environments
- Persistent URLs for ongoing demos
- Multi-service routing for full stack demos
- Quick teardown after demo completion
Microservices
- Route paths to different local services
- Single subdomain for entire service mesh
- WebSocket support for real-time services
- TCP for non-HTTP services
Technical Details
Configuration Storage
- Encrypted credentials at rest
- Version history for config changes
- Soft deletes for audit compliance
- Row-level security enforcement
Key Management
- Cryptographic key generation
- Multiple keys per configuration
- Automatic key expiration
- Instant key revocation
Included in All Plans
Tunnel configuration management is included in every ASD subscription. Higher tiers unlock more concurrent tunnels and team features.
Developer Documentation
Learn how to create and manage tunnel configurations with our CLI and API documentation.
View Documentation