w wokku
Get Started
~/docs
/
database

# Create & Link Add-ons

Enable shared add-ons on a box at creation or later; upgrade to dedicated from the box settings tab. Full CLI, API, and MCP reference.

Updated 2026-05-31 · Edit on GitHub ↗

Wokku add-ons work at the box level, not as standalone resources. You pick which shared engines to enable per box at creation, and you can add or remove them later from the box settings.

Enable shared add-ons at box creation

Go to Boxes → New Box. Under Add-ons, check the engines you want. Free plan boxes only show Postgres and Redis; paid plans show all five.

Enable a shared add-on later

Go to the box → Settings → Add-ons → toggle the engine on.

Disable a shared add-on

Disabling removes the tenant and injects null into the env var. Your data is kept for 24 hours; re-enabling within that window restores it.

Go to box → Settings → Add-ons → toggle the engine off → confirm.

Upgrade a shared add-on to dedicated

Upgrading provisions a single-tenant container, migrates data (for Postgres and Redis), flips the connection URL, and restarts the box. Uses one slot from your plan’s dedicated quota. See Dedicated upgrade for the full flow.

Go to box → Settings → Add-ons → click Upgrade to dedicated next to the engine.

Connection URL env vars

When an add-on is enabled, Wokku injects the connection URL into the box’s environment. The same var name is used whether the engine is shared or dedicated.

Engine Env var
PostgreSQL DATABASE_URL
MySQL DATABASE_URL
MongoDB MONGO_URL
Redis REDIS_URL
Memcached MEMCACHED_URL
RabbitMQ RABBITMQ_URL
Meilisearch MEILISEARCH_URL

See also

Was this page helpful?