Build backends by defining the domain.
BVER is a domain-first runtime for building services and platforms. You define References, Jobs, and Orchestrators. BVER generates consistent APIs, execution wiring, validation, and tooling—so you can focus on the domain.
Pointer-based addressing REST + MCP ops SSE live updates Adapters
Example: reference pointers
What BVER builds
References
Persistent domain objects owned by a service. Versioned changes, diffs, and triggers are first-class.
- CRUD and list operations
- Version history + diff
- Optional dynamic kinds
Jobs
Deterministic compute tasks. Tracked execution with status, retries, and emitted events.
- Celery-backed execution
- Status persistence
- Uniform operation surface
Orchestrators
Multi-step workflows that compose operations across services—without breaking ownership boundaries.
- Cross-service composition
- Event-driven automation
- Pointer-based resolution
Quickstart
Install runtime
Runtime libraries are permissively licensed and designed for broad reuse.
Install sandbox + CLI
Sandbox
What it does
- Validates service manifests and cross-service pointer contracts
- Streams live build/run logs via SSE
- Manages local cluster lifecycle (compose, restart, diagnostics)
Design goals
- Local-first: install and run on a single VM or workstation
- Thin clients: CLI + VS Code plugin + optional web UI
- Strict boundaries: cross-service references are pointers, not embedded objects
Documentation
Roadmap (near-term)
v0.1
- Sandbox daemon: config, repo scan, cluster start/stop, restart service
- SSE streaming runs + logs
- CLI parity for all daemon functions
v0.2+
- Pointer validation: service/repo/path checks against manifests
- Manifest aggregation + cluster-wide diagnostics (refs/jobs)
- Optional binaries / deb/rpm packages for easy installs