01
Model the backend as metadata
Define data, relationships, access, files, flows, and admin behavior from one inspectable model.
Cloud • Open Source • Developer First
Enfyra programmable backend platform
Build a backend from metadata, get REST APIs and admin UI immediately, then customize the parts that make your product different. Start on Enfyra Cloud, or run the open-source runtime on your own infrastructure.
Self-host with Docker
docker run -d --name enfyra -p 3000:3000 -v enfyra-data:/app/data enfyra/enfyra:latestRun the open-source runtime locally when you want full control
API
Generated REST, customizable behavior
Meta
Metadata-driven schema and admin UI
Runtime
Files, realtime, flows, and operations
Multi-DB
PostgreSQL, MySQL-compatible, MongoDB
Core model
Generated where it should be, programmable where it matters.
Enfyra is a backend control plane where metadata, custom code, permissions, runtime cache, deployment choices, and admin UI stay connected.
02
Expose generated APIs immediately
REST APIs are ready as the model changes, with permissions and common query controls already wired in.
03
Override behavior with code
Add custom logic, workflows, and extension UI where the product needs more than generated CRUD.
04
Run it where the product needs it
Start with an isolated Enfyra Cloud project, then keep the option to run the open-source runtime on your own database, storage, and infrastructure.
Runtime surface
The parts teams normally stitch together are first-class.
Start with generated APIs, then bring in auth, permissions, files, realtime, workflows, and extensions as the product grows.
PostgreSQL MySQL MariaDB MongoDB
runtime reload
No-downtime changes
Tables, routes, GraphQL schema, guards, permissions, flows, packages, and websocket definitions reload through the running cluster. The app keeps serving while metadata changes land.
no restartcache invalidationcluster reload
Realtime runtime built into the app model
websocket handlers reloadSocket gateways, rooms, user targeting, broadcasts, and live table-driven flows run through the same sandbox and metadata runtime. Change websocket handlers without restarting the app.
Realtime
websocket handlers reloadconst { roomId } = @BODY;
if (!roomId) @THROW.badRequest("roomId is required");
@SOCKET.join(`orders_${roomId}`);
@SOCKET.emitToRoom(`orders_${roomId}`, "orderLive", {
userId: @USER.id
});
return { joined: roomId };active
@SOCKET
active
rooms
active
user events
active
broadcasts
Schema engine
Create SQL or Mongo-backed data models with relations, validation, generated forms, and metadata access rules.
PG-compatibleMySQL-compatibleMongoDB
Dynamic API layer
Generated REST routes support filters, fields, sort, pagination, permissions, and route-level publishing.
GETPOSTPATCHDELETE
Security model
JWT auth, roles, route permissions, metadata guards, field permissions, and column rules work together.
RBACGuardsField accessValidation
Programmable runtime
Custom logic and guided test runs give teams a controlled escape hatch when generated behavior is not enough.
HooksHandlersWorkflowsPackages
Operational systems
Files, realtime, cache, workflows, and runtime visibility live beside the API and admin experience.
CacheFilesRealtimeFlows
Admin extensibility
Generated admin UI can be extended with custom Vue pages, widgets, menus, and header actions.
Vue SFCMenusExtensionsForms
Architecture
One place to shape the backend, the API, and the runtime.
Enfyra keeps the model, generated APIs, access rules, custom logic, admin tools, and deployment path close enough that teams can move quickly without losing control.
1
Admin app
collections, forms, permissions, docs, and runtime tools
2
App API
generated REST, auth, files, and optional GraphQL
3
Custom logic
hooks, handlers, workflows, and extensions
4
Cloud or self-host
managed Enfyra Cloud projects, or your own database, storage, cache, and deployment environment
model changes -> generated API -> permissions -> custom logic -> Cloud or self-hosted runtime
Who it is for
Built for teams that need backend leverage without giving up deployment control.
Internal tools where schema, API, forms, and permissions should evolve together.
Teams that want to start on a managed Cloud project without giving up the option to self-host later.
Projects that need generated REST now, with optional GraphQL per table when it fits.
Workflow-heavy business systems that need files, realtime, and admin extensions.
Start building
Start on Enfyra Cloud, then customize what matters.
Create an isolated Enfyra project, inspect the generated API, and move deeper into the runtime when your product needs custom behavior.
Self-host optionUse Docker or manual installation when you need to run Enfyra on your own infrastructure
npx @enfyra/create-server my-enfyra-server && npx @enfyra/create-app my-enfyra-app