Coming from Convex
Nimbus implements a Convex-compatible backend: the same function model
(queries, mutations, actions, HTTP actions), the same convex/ project
layout, schema and validators, scheduling and crons, and reactive
subscriptions — self-hosted in a single binary.
What carries over
Section titled “What carries over”- Authoring.
convex/directory,defineSchema/defineTable, thevvalidator builder,query/mutation/action/httpAction, internal functions, and"use node"actions on the Node compatibility runtime. - Clients. The Convex-compatible npm surface (
convex/reacthooks, browser and HTTP clients) pointed at your local deployment URL. - Workflow.
nimbus devwatches, runs codegen, and serves reactive updates the waynpx convex devdoes — entirely locally.
Try it
Section titled “Try it”nimbus init convex my-appcd my-appnimbus devOr point Nimbus at an existing Convex project directory and run
nimbus dev from its root.
What differs
Section titled “What differs”Nimbus is pre-launch and tracks compatibility honestly rather than claiming parity: some surfaces are complete, some are bounded, and Node-runtime coverage is documented per version. The compatibility matrix in Reference is the source of truth for what is supported today.
Next steps
Section titled “Next steps”- Developer quickstart — the five-minute path.
- Developers — per-feature guides as you build.
- Concepts — how Nimbus’s engine differs under the hood.