3
managed ecosystem components
ECOSYSTEM CONTROL PLANE
One binary. One seamless interface. Deploy, configure, supervise, and update NullClaw, NullBoiler, NullTickets, and additional ecosystem components—all from a unified high-performance dashboard or CLI.
managed ecosystem components
CLI commands for automation
single binary — Zig + embedded Svelte UI
multi-instance: run N copies side by side
Manifest-driven setup wizard with intelligent component linking (e.g., NullTickets to NullBoiler). Fully accessible via browser or terminal.
Robust lifecycle management: start, stop, restart, and automatic crash recovery with exponential backoff. The hub daemon supervises all ecosystem instances.
Continuous HTTP health probing, real-time dashboard status cards, and live state updates delivered via Server-Sent Events (SSE).
Intuitive structured editors for NullClaw, NullBoiler, and NullTickets configurations, with a raw JSON fallback layer for advanced users.
Real-time log tailing and streaming per instance. Analyze logs directly within the browser dashboard or follow them from your terminal.
Seamlessly download new component versions, automatically migrate configurations, and safely rollback on failure. Update individually or simultaneously.
Automatically bind dependent components (NullTickets → NullBoiler), configure trackers natively, and inspect orchestrator queues from a unified UI.
A premium browser dashboard for human operators, paired with a powerful CLI for automation scripts—both offering complete feature parity.
High-performance HTTP server, robust process supervisor, installer, and manifest engine. Runs in long-lived server mode or transient CLI mode.
Statically generated SvelteKit application embedded directly into the binary overhead-free. Modular UI components load dynamically using Svelte 5.
Ecosystem components publish declarative manifests specifying their setup, configuration, and health parameters. NullHub acts as the universal interpreter.
Zero external database required. All state—configurations, runtime instances, binaries, logs, and manifest caches—persists neatly in a local directory.
The fastest, most lightweight, and fully autonomous AI agent execution runtime written from the ground up in Zig.
Advanced workflow orchestrator handling multi-step agent executions with manual approvals, automatic retries, and intelligent worker dispatch.
Comprehensive execution-state backend managing task pipelines, leases, requisite gates, dependencies, and generated artifacts.
nullhub # Start server + open browser
nullhub serve [--port N] # Start server without browser
nullhub install <component> # Terminal wizard
nullhub uninstall <c>/<n> # Remove instance
nullhub start <c>/<n> # Start instance
nullhub stop <c>/<n> # Stop instance
nullhub restart <c>/<n> # Restart instance
nullhub start-all / stop-all # Bulk start/stop
nullhub status # Table of all instances
nullhub status <c>/<n> # Single instance detail
nullhub logs <c>/<n> [-f] # Tail logs (-f for follow)
nullhub check-updates # Check for new versions
nullhub update <c>/<n> # Update single instance
nullhub update-all # Update everything
nullhub config <c>/<n> [--edit] # View/edit config
nullhub service install # Register as OS service (systemd/launchd)
nullhub version # Print versionInstance addressing uses {component}/{instance-name} everywhere.
# Clone and build NullHub
git clone https://github.com/nullclaw/nullhub.git
cd nullhub
zig build
# Launch — opens browser to http://nullhub.localhost:19800
./zig-out/bin/nullhub
# Or install a component directly from the CLI
./zig-out/bin/nullhub install nullclaw
./zig-out/bin/nullhub install nullboiler
./zig-out/bin/nullhub install nulltickets
# Start everything
./zig-out/bin/nullhub start-all
# Check status
./zig-out/bin/nullhub statussrc/
main.zig # Entry: CLI dispatch or server start
cli.zig # CLI command parser & handlers
server.zig # HTTP server (API + static UI)
auth.zig # Optional bearer token auth
api/ # REST endpoints (components, instances, wizard, ...)
core/ # Manifest parser, state, platform, paths
installer/ # Download, build, UI module fetching
supervisor/ # Process spawn, health checks, manager
wizard/ # Manifest wizard engine, config writer
ui/src/
routes/ # SvelteKit pages (dashboard, install, instances, settings)
lib/components/ # Reusable Svelte components
lib/api/ # Typed API client
lib/stores/ # Reactive state (instances, hub config)
tests/
test_e2e.sh # End-to-end test scriptBackend runtime, HTTP server, process supervisor, and native build system.
Frontend with static adapter, embedded into the binary at compile time.
REST API for all control operations. SSE for live streaming logs and status.