Hello everyone,

I would like to introduce and invite you all to try out a new BaaS: Enfyra.

When it comes to quickly building a backend for a new product, Supabase is often the first choice that many teams think of.

With a database, API, authentication, storage, and real-time capabilities right from the start, it helps an idea go from zero to a functioning app very quickly.

I am building Enfyra with that same spirit.

But Enfyra is built to accommodate a rapidly changing landscape: AI is no longer just helping to write code — AI is becoming a partner in building and operating products.

────────────────

🤖 WHEN AI MEETS BACKEND

AI can create interfaces in minutes. However, the backend often remains a more challenging area:

• AI must infer the schema

• It needs to find existing APIs

• It must understand permissions

• It needs to know where the business logic is located

• And every small change can lead to commits, CI/CD, and deployments

Enfyra aims to make the backend a surface that both developers and AI can work on more clearly.

────────────────

⚡ LIVE METADATA BACKEND PLATFORM

Enfyra is a live metadata backend platform.

Data models, API routes, permissions, hooks, handlers, workflows, real-time events, and admin extensions are defined by metadata, which is then activated into a running runtime.

This creates a common source of truth for the product:

• Developers see it in the admin console

• AI can read and manipulate it via MCP

• Runtime uses that very metadata to run APIs, permissions, workflows, and the admin UI

Instead of having AI guess the backend from the codebase or having to write a new service, Enfyra provides a structured way for AI to explore and modify the running backend.

────────────────

🎬 VIDEO DEMO

Codex connects directly to an Enfyra instance through MCP, reads the system's metadata, views existing tables and configurations, then adjusts the extension/admin UI and backend configuration directly on the running runtime.

AI can work with the data model, API, permissions, workflows, and admin experience of the product — through a clearly structured backend.

────────────────

🧩 WHAT DOES ENFYRA OFFER?

• Intuitive schema/collection creation

• Automatically generated REST and GraphQL APIs

• Authentication, permissions, file storage, and real-time

• Custom routes, hooks, and handlers for business logic

• Workflows based on triggers or scheduled runs

• Custom extension pages and widgets for the admin console

• PostgreSQL, MySQL/MariaDB, and MongoDB

• MCP to connect AI coding tools with Enfyra runtime

Changes related to metadata such as routes, permissions, handlers, workflows, or extensions can be activated into the runtime without needing to restart the entire server.

CI/CD is still needed for code, infrastructure, and controlled releases. But Enfyra's goal is to ensure that changes related to how the product operates do not always lead to a deployment cycle.

────────────────

🔍 SUPABASE AND ENFYRA

Supabase remains a very strong choice, especially if you want a Postgres-first platform with a complete ecosystem.

Enfyra is not built to suggest that everyone should abandon Supabase.

I built Enfyra for when the backend needs to become a programmable and flexible part of the product — especially in the era of AI coding.

────────────────

☁️ ENFYRA CLOUD BETA

Enfyra Cloud is currently in beta.

You can self-host Enfyra if you want full control over the infrastructure. With Enfyra Cloud, the goal is to help you start a project even faster.

Currently, I do not have the budget to offer a widespread free plan. But if you are building a product, using Supabase, Directus, Strapi, or a similar platform, and want to try how