Skip to content

Current feature status

This release snapshot uses source commit 747f4289840955f8df4981fb00ec7765501c02aa. Download source metadata.

Runtime target: K3s/Kata on the development node; Kraft compatibility via Kraftplane

Status: maintained with compiler and generated-runtime changes

backend.fast V1 is not fully implemented yet. The current implementation is a beta subset with checked compilation, generated Go/OCI builds for Kata, bounded runtime behavior and app observability. Kraft remains a compatibility path.

Generated behavior includes compiled Go functions, model declarations, cache, transactional events, job schedules, bounded files, native auth, and telemetry. Requests call generated functions rather than interpreting body operations. The compiler uses checked SQL helpers and source declarations. It does not infer behavior from route names. Vercel serves the dashboard; Kraftplane owns its scoped APIs and app control.

validate, generate, build, sdk, and deploy require executable runtime support. They reject unsupported bodies and helper functions before writing artifacts. Checked handlers, jobs, and File values execute in Minidesk through normal CLI/Kata/browser tooling. The milestones 4–5 report records public SDK, owner controls, recovery, backup, and Small workload acceptance. kraftplane bfast dev reports that its watch/run workflow is not implemented. The local compiler sdk command writes the client file. Portable bfast sdk and bfast openapi download contracts from the selected owned deployment.

November 16 BF-160 activates local-v1 for fresh native app auth. This profile removes commercial stored-user and global session caps. Separate operation budgets, password concurrency, disk headroom and bounded cleanup remain. Public checks pass with 21 users and more than 32 sessions; source recovery tests cover 1,500 users and 65 sessions. Existing profiles remain explicit. Read the live deployment report.

Legend:

  • Done: supported in parser/semantic/codegen/runtime.
  • Partial: represented or checked, but runtime/codegen behavior is incomplete.
  • Missing: not implemented beyond possibly being documented.

M1 permits a feature to reject compilation with a repair-oriented diagnostic. A Partial row therefore needs its supported/rejected boundary; it does not automatically require complete V1 implementation before M1. The M1 review does not change language behavior or promote partial rows without evidence.

Feature Status Notes
app "name" Done Exactly one app is required.
model Name { ... } Partial Parsed and generates a SQLite table. Each model requires an immutable non-optional ID. Generated runtime still uses JSON-backed rows.
type Name struct { ... } Partial Parsed and emitted as Go struct; selected CRUD routes validate JSON body fields, types, optional values, and defaults, but full response lowering is incomplete.
event Name { ... } Partial Typed emission and generated handlers execute transactionally. General body expressions remain limited below.
Annotated func Partial Parsed and checked; full body lowering is missing.
Basic types Partial Parser and semantic support exists for V1 basic types. Selected query storage normalizes Time, Date, and Duration; broader runtime storage remains incomplete.
Optional T? Partial Type/default validation and selected guarded CRUD writes exist; broader runtime behavior remains limited.
Arrays []T Partial Parsed and checked; selected CRUD array literals and typed JSON body arrays run, but broader array behavior remains limited.
Defaults Partial Selected scalar, empty-array, nil, and now() defaults are type-checked and applied to JSON body records and model creates.
Field annotations Partial @index and @unique generate model indexes. String/text @min and @max enforce inclusive Unicode code-point lengths; @enum enforces exact string membership. Checks apply to nested records, defaults, CRUD, events, and responses. Unsupported constraint types, duplicate constraints, contradictory bounds, and invalid defaults reject compilation. Numeric and array constraints remain unsupported.
Feature Status Notes
@api METHOD /path Partial Method/path validation rejects malformed, overlapping, system-reserved routes. Checked CRUD/query bodies compile into direct Go functions. Other bodies reject compilation with a repair diagnostic.
@auth none/user/admin Partial Caller user/role headers grant no authority. Protected routes fail closed without trust configuration. Fresh owned apps select embedded auth after BF-151 public CLI and dashboard checks. Authboss/SCS use the app SQLite database; the business transaction checks current local users and roles. The gateway signs a separate routing proof and verifies app TLS. Existing shared apps retain current-session gateway checks. Owner-scoped user administration and authenticated CLI requests pass for public Counter and URL Shortener apps. BF-152 adds complete offline native recovery, public verification/reset pages, and measured Counter/Shortener qualification on both Small and Medium at 40 mixed requests/s. Independent R2 download and isolated native recovery now pass under BF-154/BF-155. Physical reboot, replacement-host recovery, larger native payloads and broader V1 acceptance remain open. This does not close the remaining BF-133 or BF-145 gates. A body that reads auth.user requires a user-bearing auth rule.
@auth user owns Model.field Partial Ownership field validation exists. The new runtime scopes same-model reads and writes to verified user context inside the transaction. Counter, URL Shortener, and query/ownership fixtures pass. BF-151 adds public native checks for same-app ownership, role changes, revocation, and data isolation. Broader V1 acceptance remains open.
@cache 30s Partial GET-only semantic validation and generated bounded in-memory response cache; BACKEND_FAST_CACHE_MAX_BYTES or BACKEND_FAST_CACHE_MAX_MIB sets its per-app capacity (64 MiB default), and d and w V1 duration suffixes are normalized at runtime.
@cache 30s key=user,params Partial GET-only validation requires params for any API parameter and user for user-auth routes. Ownership routes reject TTL caching. Deterministic keys run in the app microVM, and cache contents clear on app restart.
@cache invalidate ... Partial Strict target syntax and successful-mutation generation replacement discard stale concurrent fills. One token per declared target stays outside the evictable response store.
@on EventName Partial Checked handlers compile into Go. The generated Minidesk race fixture verifies transactional delivery and failure behavior. Minidesk passes public requests and owner CLI/dashboard checks.
@once key=... Partial A scalar event field supplies the key. Business effects and the durable receipt commit together. Duplicate and replay tests pass; the ledger stops at 10,000 keys rather than evicting receipts.
@job hourly/daily/every Duration Partial Generated jobs persist schedules and run history. UTC hourly/daily and duration schedules pass due, concurrent-claim, restart, and missed-interval tests. Bounded history, normal restart/redeploy, automatic runs, and owner CLI/dashboard controls pass live Minidesk checks.
Feature Status Notes
Go-compatible block extraction Done Bodies are parsed with Go parser after duration literal normalization.
Restricted AST validation Partial Goroutines, channels, defer, pointers, interfaces, arbitrary package calls, and unsupported stdlib roots are rejected.
storage.save(...) type check Partial Checked File values compile. storage.save verifies an uploaded reference and canonicalizes its metadata in the business transaction. Ownership and SQLite backup/restore tests pass. Strict SDK checks, public file transfers, restart/redeploy readback, and verified snapshot coverage pass.
emit(Event{...}) validation Partial Selected lowered routes check event fields and write typed pending outbox rows; general event expressions remain incomplete.
Database collection validation Partial database.<collection> must map to a declared model collection; selected query fields, comparisons, order, limits, terminals, return shapes, create values, field writes, and direct CRUD calls are checked.
Full body lowering Partial Checked CRUD/query, event, job, and storage bodies compile into Go statements. The request path no longer interprets body plans. General branches, helpers, loops, and other expressions remain explicitly rejected. Minidesk passes generated race tests and normal CLI/Kata/dashboard acceptance.
Feature Status Notes
Go HTTP server Partial Generated and compiled for beta examples.
Kraft packaging Partial Kraftfile/Dockerfile/rootfs are generated and deployable.
SQLite model storage Partial JSON-backed model tables and selected field indexes. Generated schema names reject system, keyword, case-folded, table, and index collisions. Unique conflicts return 409. Startup validates model rows and normalizes legacy typed values in one transaction. New configured Kata apps persist WAL/FULL/NORMAL. Legacy explicit profiles retain their settings. MEMORY journaling does not provide crash-safe transactions.
Running database backup Partial New Kata apps persist WAL/FULL/NORMAL and backup enabled. The installed schedule uses private --bf-backup-reserve with an owned LVM snapshot and host WAL preparation. Small/Medium checks pass with 896 MiB of payload at 40 mixed requests/s. Actual scheduling, encrypted restore, interrupted-worker retry, deletion cleanup, and paired activation pass. Explicit logical export remains qualified at 64 MiB and 2 MiB/s. Unsupported images fail without fallback. Verified R2 app/control copies and isolated downloaded-app readback pass under BF-154/BF-155. Replacement-host recovery and automatic product restore remain open in BF-132. No public endpoint or sidecar is added.
Typed database/query layer Partial Generated CRUD/query plans support scalar filters, order, limit, terminals, filtered delete, source-position filter snapshots, stable guarded writes, exact 64-bit integers, arrays, string joins, fixed-width UTC times, and normalized signed duration values. Each lowered function uses one SQLite transaction. Storage remains JSON-backed.
Event outbox Done Declared emission atomically writes the event and its handler deliveries. Generated Go handlers use bounded retries and atomic once receipts. Generated race and live checks cover duplicates, rollback, exhaustion, replay/skip, owner controls, and retained state. Interrupted-claim tests also pass.
Jobs Done Persisted app-local schedules and transactional execution pass generated Minidesk race tests. One worker coalesces missed intervals. Normal restart/redeploy, bounded history, automatic runs, and owner controls pass live acceptance.
Cache Partial GET TTL response caching, declared mutation invalidation, generated configurable in-memory LRU capacity (64 MiB default), Prometheus-compatible cache metrics, bounded JSON diagnostics, and tenant-scoped retained dashboard counters are generated; distributed/shared invalidation is missing.
File storage Done Authenticated multipart upload and app-local SQLite BLOB persistence pass generated ownership, size, canonical metadata, cleanup, and backup/restore tests. Limits are 2 MiB/file, 64 MiB and 1,000 files/app. Strict SDK checks, public file transfers, restart/redeploy readback, and verified snapshot coverage pass.
Account object storage Partial Fresh native Kata apps now use private R2 File routes, canonical SQLite metadata, durable upload keys, verified expired-upload cleanup and a shared 10,000,000,000-byte account allowance. The 2 MiB transfer bound remains. Public CLI and Vercel dashboard usage views pass. A version-3 scheduled archive restores exact object bytes after source deletion. Existing apps retain their SQLite backend. Full-account backup duration, automatic customer restore and permanent purge remain open. See the operator procedure.
OpenAPI Done Checked routes now distinguish input/output records, constant/dynamic defaults, optional fields, enums, int64, opaque app bearer tokens, error envelopes, void responses, and managed File endpoints. Contract fixtures and paired public SDK/browser download checks pass. Hashes pin downloads to the selected deployment.
TypeScript SDK Done Strict TypeScript checks pass for Counter, Shortener, and Minidesk. Input shapes preserve omission/default rules; output fields remain present. The client supports enums, exact bigint JSON, typed HTTP errors, opaque bearer tokens, standard File uploads, references, and downloads. Shared record descriptors stay linear. Node execution and downloaded-client public HTTPS acceptance pass on Kata. Native cross-origin browser policy remains unchanged. See the SDK contract.
Cross-origin browser SDK Missing Node SDK use and the registered app origin are qualified. Browser frontends on other origins need a separate registered-origin/CORS design; no wildcard policy is implied.
/healthz Done Generated apps expose health.
/__bf/metrics.json Partial App-level route metrics plus bounded in-memory cache snapshots exist.
/__bf/metrics.prometheus Partial Native request/status counters, classic duration histograms, admission, process/guest cgroup, SQLite transaction, cache counters, and cache gauges are generated. Missing source fields stay absent. BF-116 adds verified Kata host/PVC measurements and the authenticated default UI. Pressure and overhead qualification remain open.
Native telemetry delivery Partial Generated apps emit bounded structured stdout and optional sampled OTLP traces. Request handlers no longer emit duplicate blocking text logs. The private receiver checks pod credentials and assigns identity. New generated apps omit the duplicate trace buffer and the retired records endpoint. Full failure, cost, and scale qualification remain open in BF-116.
/__bf/metrics/current.json Partial Bounded current diagnostic snapshot includes safe cache definitions, counters, and bounds without cache keys, values, responses, or local history.
/__bf/test Partial Kraftplane redirects this path to the authenticated telemetry dashboard. The November 8 paired release denies public raw snapshots and requires a separate platform-reader assertion at their generated handlers. The scoped Data API retains model snapshots after a current data:read grant check. Native owner work controls now cover event deliveries, job history/actions, and file metadata. They use separate current-owner authority rather than Data API grants.

Operational input limits apply before compilation: backend.fast files must be regular files of at most 256 KiB. Project generation rejects output above 2 MiB or 64 files before writing generated files. These limits do not change supported V1 semantics. Configured Kata deploy/redeploy runs parsing and generation inside the bounded compiler Job. The generated-source compatibility archive retains a separate 512 KiB/64-file limit; see bounded builds. New configured DSL images preserve the exact submitted backend.fast alongside generated files. Its separate 256 KiB allowance does not increase generated output limits. Build acceptance checks byte equality. Existing backups remain readable without this file; the change does not add DSL language support.

This matrix records feature support; it does not prioritize work. The M1 release order is in docs/roadmap/m1.md, and the implementation details for the current slice belong in its linked ExecPlan.