For developers
Debug on your laptop against the real stack
Run the service you are changing in your IDE, with breakpoints, against the team's database, identity provider and broker. fadebox connect puts each of them on localhost on its own port, through Fadebox itself: no VPN, no client to install beyond the CLI, on Linux, macOS and Windows.
What you get
No stack on the laptop
The database, the identity provider and the broker run on the team's Docker hosts. Your laptop runs your service and your IDE.
Your tools, unchanged
psql, DBeaver and the IDE's database view connect to localhost:5432. The local port is remembered per instance, so a saved connection keeps working.
Access stays governed
Each connection is allowed by your project role and the instance's gate, and written to the audit log. An open instance's URLs may be public; its database is not.
How it works
- 01
Deploy a personal instance
fadebox instance up dev-alice --personal --wait brings up your own copy of the environment, at the versions the team runs.
The deploy loop → - 02
Connect from your laptop
fadebox connect dev-alice prints a line per service, postgres 5432 → localhost:5432, and keeps the ports open until Ctrl-C.
Connecting with fadebox connect → - 03
Run your service against localhost
Point its configuration at localhost and start it from the IDE. When the team's versions move, redeploy: only what changed restarts, and your data stays.
Redeploy restarts only what changed →
Other use cases
Running on your own host in 10 minutes
Two containers. Works offline. Your data never leaves your infra.