Nango on your server

Run Nango on your own infrastructure when you want its database to hold connected-service login access. DorkOS keeps the Nango server address and secret key. Nango keeps the service tokens.

This route is an early alpha. It is tested against a local fixture, not a real self-hosted Nango deployment. It can connect and inventory accounts. Agent actions and notifications remain unavailable because the route does not provide the exact trusted metadata they require.

What you need

a self-hosted Nango server;
its secret key;
the server's NANGO_ENCRYPTION_KEY;
its base URL.

DorkOS does not use Nango's paid MCP features or expose a generic credentialed proxy.

Set it up

Set Nango's encryption key

Create a 32-byte key in base64:

openssl rand -base64 32

Set the same value as NANGO_ENCRYPTION_KEY on the Nango server and in the DorkOS server environment. DorkOS checks that it decodes to exactly 32 bytes. It refuses to start this route when the value is missing or malformed.

Set the server address

Set NANGO_BASE_URL to the Nango origin, such as http://localhost:3003. DorkOS rejects an invalid URL during startup.

Save the secret key

Open Connections, expand Composio & Nango, and save the Nango secret key. DorkOS keeps it in the local encrypted credential store. Saving or removing the key updates the route without a restart.

Connect an account

Choose a service and complete the sign-in through your Nango server. The account appears in Connections after Nango reports it as active. It remains unavailable to agents until this route can provide immutable action versions and safe classifications.

Current limits

DorkOS can list and disconnect a connected Nango account. It cannot grant that account's actions or notifications in this release. This is a capability limit, not a broad permission. DorkOS shows the route as unavailable for those uses.

If you need reviewed actions now, use Composio. If you already run a remote MCP server, read Raw MCP server.

Nango on your server

On this page