Skip to content
Fluxify

versioning & releases Snapshot working copies. Promote with automated gates.

Development runs your working copy as you edit. Production serves only the version you promoted — verified by automated test suites and compiler checks before a single request flips over.

Read the docs
production serves live traffic development hot-reloads saves v1 past release PROD · v2 LIVE Next: Promote v4 runs 5 quality gates → v1 Initial draft Sarah · 3d ago v2 Add JWT auth Alex · 2d ago v3 Retry logic Sarah · 1d ago v4 Rate limiter Alex · 2h ago HEAD Working ● uncommitted
A git-like tree for backend releases: Development holds your commit history and active working copy. Production stays locked to promoted versions until you release.

the working copy

Edit freely on dev. Production never flinches.

The route or workflow you edit is your working copy. Every save you make goes live on your development worker immediately, while production keeps running the promoted version.

Saved in a version

What the route is

Immutable snapshot · frozen into release commits

  • The blocks and wiring
    Canvas AST

    Every block type, position, and connection

  • Route path & method
    POST /api/v1/orders

    Endpoint path and HTTP method contract

  • Request & response schemas
    OpenAPI

    Zod input schemas and versioned status-code response schemas

  • Timeout & settings

    Execution time limits and failure configurations

  • Attached middlewares

    Ordered before and after execution chains

Stays live

How you run it

Runtime controls · toggle with zero redeployment

  • Active switch
    0ms flip

    Turn route on or off instantly without creating a version

  • Development switch
    dev only

    Enable or isolate a route in development only

  • Recording & tracing
    live trace

    Toggle debugging trace recording on either environment

  • Production route badge
    live status

    Promoted endpoints carry a production rocket chip in the routes list

  • Environment values
    dev · prod

    Dev vs prod database credentials and config secrets

automated gates

Five checks before production switches.

Promoting a version runs automated checks first. If any check fails, the promote is refused, production keeps running the old version, and the log tells you what broke.

RELEASE CANDIDATE v4 · "Add rate limiter & retry" → Target: production 5 / 5 GATES PASSED ✓ 1. Compiles Compiled to standalone Bun JS module · 0 cycles · valid AST PASS 12 ms ✓ 2. Production values All cfg: secrets & integrations verified in production environment PASS 4 ms ✓ 3. Path available Route path is free · zero collision against active production routes PASS 1 ms ✓ 4. Dependencies live All referenced custom blocks and middlewares are promoted in production PASS 6 ms ✓ 5. Test suites Ran 3 test suites (12 cases) against v4 on dev worker · 100% passed PASS 46 ms Verified on development worker · Swapped into production route table with zero downtime
Promoting a version runs five automated gates. Production only switches when every check passes, including all attached test suites.

all 5 checks pass

Zero-downtime hot swap

Production workers load the newly compiled module from NATS KV in place. In-flight requests finish on the version they started with.

any check fails

Instant fail-safe abort

If a test case fails, a secret is missing, or a path collides, the promote is rejected. Production never stutters, and the audit log records the exact reason.

shared libraries

Custom blocks & middlewares have versions too.

A custom block or middleware is shared by every route that calls it. Promoting a block updates all production routes using it, with Used By dependency tracking and delete guards.

  • Promote once, update all atomic

    Promoting a shared block updates all production routes calling it with zero downtime.

  • Used By dependency tracking caller graph

    Inspects every calling route, workflow, and test suite before changes go live.

  • Breaking delete guards delete guard

    Prevents deletion while any route's working copy or promoted release relies on it.

environments

Dev vs Prod: isolated data and workers.

Development workers handle live edits and test suites on local or dev data. Production workers run strictly promoted versions with production vaults and zero-downtime hot swaps.

Development
FLUXIFY_ENV=development

Development worker

Rapid iteration on live working copies & dev data

  • Instant hot reload

    Working copy edits go live immediately on save with zero restart delay.

  • Sandboxes & test suites

    Executes automated suites and private sandboxes against dev data.

  • Full execution traces

    Captures step-by-step block inputs, outputs, and logs for fast debugging.

Production
FLUXIFY_ENV=production

Production worker

Protected runtime lane serving live customer traffic

  • Gated releases only

    Serves only versions that passed compiler, security, and test checks.

  • Zero-downtime hot swap

    Production loads compiled modules from NATS KV without dropping in-flight requests.

  • Production vaults

    Strict production database credentials, secrets, and integration keys.

next Workflows & triggers Background work from schedules, queues and routes, with batching.