Skip to main content

Roadmap

Fascia is under active development. This page shows what's available now, what we're building next, and where we're headed. Priorities may shift based on community feedback and market signals.

Now -- Available Today​

These features are live and ready to use.

  • Entity CRUD Portal -- Auto-generated web interface from your specs. Browse records, create and edit data, execute Tools, and manage status transitions without writing frontend code.
  • Tool Execution -- Define API endpoints, webhook handlers, and cron jobs as structured specs. Fascia's Go-based executor runs them deterministically inside your cloud.
  • Flow Graphs -- Visual DAG editor for Tool logic. Chain reads, writes, transforms, conditionals, retries, and external calls into reliable execution sequences.
  • Built-in Auth -- Email/password registration, OAuth providers (Google, Apple, Kakao, Naver, GitHub), RBAC with role-based access control, and row-level security. All spec-driven.
  • Safety Agent -- Multi-model AI cross-checking at design time. Detects unsafe patterns, suggests fixes, and generates test cases before deployment.
  • Risk Engine -- Every Tool gets a risk classification (Green / Yellow / Red) based on its flow patterns. Red-level Tools are blocked from deployment. No exceptions.
  • BYOC Deployment -- Deploy to your own GCP project. Your data stays in your infrastructure. Fascia never stores or processes your business data.
  • Hosted Plan -- Managed environment for quick starts. No GCP setup required. Upgrade to BYOC when you're ready.

Next -- In Development​

These are the features we're actively designing. They address the most common gaps between "works for simple apps" and "handles real-world complexity."

ForEach Node​

Process arrays and collections inside Flows. Currently, Flows handle one item at a time. ForEach enables batch operations like "send confirmation emails to all attendees" or "update inventory for each line item."

SubFlow​

Call one Flow from another. Reuse common sequences (like "validate payment and update status") across multiple Tools without duplicating nodes.

Error Edge​

Define what happens when a node fails. Route errors to compensation logic, send alerts, or trigger rollback sequences. Today, errors stop the flow. Error Edge lets you handle them gracefully.

Visual Spec Editor​

Edit Entity and Tool specs directly through a form-based UI, alongside Chat Studio. For users who want precise control over field types, status machines, and invariants without conversational back-and-forth.

Portal Customization​

Customize your auto-generated Portal with themes, field-level UI hints (date pickers, dropdowns, rich text), and layout templates. Make it look and feel like your product.

Later -- On Our Radar​

These are directions we're exploring. They're real plans, not wishful thinking, but their priority depends on what the community needs most.

  • Multi-Cloud BYOC -- AWS and Azure support in addition to GCP. Same spec-driven deployment model, more cloud options.
  • Team Workspaces -- Multi-user collaboration with role-based permissions at the workspace level.
  • Client SDK -- @fascia/client-sdk for programmatic access to your Fascia-powered backend from any frontend or service.
  • Spec Marketplace -- Share and discover Entity/Tool templates. Start from proven patterns instead of blank specs.
  • Advanced Audit Dashboards -- Time-series execution logs, deployment timeline with rollback, and real-time metrics for Tool invocations.

Design Philosophy​

Why this order? Fascia's core promise is that structured specs can express any backend logic safely. The "Next" features directly expand that expressiveness:

  • ForEach + SubFlow + Error Edge fill the gaps in what Flow graphs can represent. Once these ship, the declarative model covers the vast majority of real-world backend patterns.
  • Visual Spec Editor + Portal Customization make the existing system more accessible and flexible, without changing the underlying architecture.
  • Later items extend the platform's reach (more clouds, more users, more integrations) after the foundation is complete.

One thing stays constant across every phase: the Safety Agent and Risk Engine are never weakened. Every new node type, every new feature goes through the same safety analysis. That's not negotiable.