Dev Portal
The web UI for creating, configuring, building, and managing connectors.
The Dev Portal is the web interface for the Connector Development Environment. Everything you do with connectors — creating, configuring, building, deploying, monitoring, and releasing — happens here.
Main areas
The Dev Portal is organized into a few key areas:
Connectors
The main view. Lists all connectors your account has access to. From here you can create new connectors or click into an existing one to configure, build, and deploy it.
Connector setup
When you open a connector, you land on a multi-step setup wizard. Each step configures a different aspect of your connector:
| Step | What it configures |
|---|---|
| Connector details | Name, type, description, flow, execution mode, owner, logo |
| Version Control configuration | Git repository URL, branch, and authentication |
| Application configuration | CLI command, arguments, and health check |
| Authentication and secrets | OAuth schemas and secret references |
| Individual configuration | Form fields exposed to end-users (API keys, URLs, etc.) |
| Execution configuration | How configurations are passed to your connector at runtime |
| Type-specific configuration | Settings that depend on the connector type (datasource name, export channel, etc.) |
Steps marked as optional can be skipped for a minimal setup. The required steps depend on your connector type.
Release configuration
Once your connector is configured, the release configuration page walks you through the deployment pipeline:
- Build — builds a Docker image from your Git repository
- Sync with runtime — registers the image so it can be executed
- Sync with dev — deploys to a development site for testing
- Sync with prod — deploys to production
- Enable access — makes the connector available to users
See Build and deploy for details.
Monitoring
Track connector runs, view application logs, and debug issues. The monitoring section shows:
- Run history with status, duration, and process IDs
- Application logs at all levels (info, warning, error, etc.)
- Raw stdout/stderr output from the container
- State transition history for the connector version
See Monitoring for details.
Versions
Each connector can have multiple versions, each with its own configuration and deployment state. Versions let you develop a new iteration while the current one stays live in production.
See Versions for details.
Connector bin
Deleted connectors go to the bin first, where they can be restored or permanently removed.
What's next
How is this guide?