Bridge icon
Bridge
Service Orchestrator
ATLAS CREW SECURITY · ORCHESTRATION

One command. The whole lab running.

Bridge is the local operational console for Atlas Crew Security. Service inventory, visual config editor, log streamer, dependency-aware lifecycle. Bring up Synapse, Chimera, and Crucible together with a single command, route traffic through the closed loop, and watch what happens without manually wiring four containers.

View on GitHub ↗ npm ↗ Atlas Crew Security →
THE CONSOLE

A workspace for the lab.

Most operational tooling for security platforms is plumbing: CLI flags, Docker Compose files, environment variables. Bridge gives the lab a real workspace instead — see the services, edit configs visually, filter logs, open a port with a click. Running it should be tractable, not a project.

Bridge service orchestrator console: service inventory, configuration, and log streaming for Atlas Crew Security
Bridge console: Synapse, Chimera, and Crucible managed in one view
Service inventory
Every running service in the lab: status, port, version, dependencies. Click a port to open the service in your browser.
Visual config editor
Edit Synapse rules, Crucible scenarios, and Chimera vertical settings without leaving the console. Changes hot-reload.
Log streamer
Tail logs across all services with filters by severity, service, or trace ID. Useful when an assertion fails and you need to find out where.
Lifecycle controls
Start, stop, restart, and reset services with dependency awareness. Bridge knows that Chimera comes up before Crucible runs scenarios.
CLI

For when you'd rather not click.

Bridge ships with a CLI for cross-product orchestration. The web UI is the primary surface, but power users can drive the whole lab from the terminal for CI pipelines, scripted scenarios, or heads-down terminal sessions.

~/lab - bridge
$ npx @atlascrew/bridge up ↳ pulling synapse v0.4.1 ............................. ready ↳ pulling chimera v0.6.0 ............................. ready ↳ pulling crucible v0.2.0 ............................ ready ↳ wiring traffic: crucible → synapse → chimera ↳ console: http://localhost:8080 $ bridge status synapse : running :7421 (1m 23s) chimera : running :7422 (1m 22s) crucible : running :7423 (1m 21s) $ bridge run-scenario kafka-takeover ↳ executing 14 steps ............................... complete ↳ assertions: 11 passed · 3 failed · 0 errored $ _
SCOPE

Cross-product orchestration only.

Bridge is deliberately narrow. It handles operations that span multiple products: lifecycle, multi-product configuration, scenario execution, integrated diagnostics. It is not a wrapper around per-product CLIs. The Crucible CLI, Synapse admin CLI, and Chimera tools stay independent for product-specific depth.

Bridge does
  • Lifecycle: bridge up / down / status / reset
  • Cross-product scenarios: bridge run-scenario <name>
  • Multi-product configuration through one editor
  • Aggregated logs and diagnostics across the integrated stack
  • Service inventory + port routing
Bridge doesn't
  • Wrap crucible scenarios list or other per-product commands
  • Re-implement Synapse rule editing (use the Synapse admin API)
  • Manage Chimera vulnerability tours (use Chimera directly)
  • Replace Docker, Kubernetes, or your existing service orchestration in production

Bridge is the orchestration substrate for Atlas Crew Security.

On its own, Bridge is a local development tool for running any of the security products independently, but it is most valuable when running them together. Inside the platform, it's the substrate that makes the closed-loop lab tractable: Synapse defends, Chimera is attacked, Crucible attacks and asserts, Bridge makes them all work in one place.

See the platform →