Synapse App Builder
CommunityAI-powered low-code app builder for Laravel + Filament: visual pages, database collections, an n8n-style flow engine, end-user auth, and AI that builds whole apps. Self-hosted.
Author:
Andre Corugda
Package health
BetaAutomated checks of this plugin's Composer package
13 checks
-
Passed:
Current Laravel version supported
—
Package dependencies resolve together with current Laravel
13.0. -
Passed:
Current PHP version supported
—
Constraint
^8.2supports current PHP8.5. - Skipped: Current Symfony version supported
- Passed: Abandoned or archived — No consulted source marks the package abandoned (packagist, github).
- Passed: Commit and release recency — Active: last commit 3 days ago; last release 3 days ago.
-
Passed:
composer.lock not committed by library
—
composer.lockis absent from the released dist archive. - Warning: Dist archive is lean
- Failed: GitHub Actions pinned to SHA — View details on Plumb
- Passed: Open security advisories
- Passed: Dependabot PR responsiveness — No open Dependabot PRs.
- Failed: Dependabot or Renovate configured — No dependency updater configuration found. View details on Plumb
- Skipped: Dependency update cooldown configured
- Failed: Provides a security policy — View details on Plumb
filament/
namespace. Review the source and install at your own risk. Found
malware or an unresolved security issue the author won't
address?
Report it
.
Documentation
Synapse is a self-hosted, low-code app builder that lives inside the Laravel + Filament admin you already run. You build pages (GrapesJS), define your own data tables (Collections), wire automations (Flows), gate everything behind your app's own users and roles — and an optional AI layer can generate or refine the whole thing from a plain-language brief. Everything you build is stored as ordinary database rows, and nothing leaves your server.
These docs are the reference: how it installs, how each subsystem works, the exact config keys, routes, table names, field types, node shapes and query syntax — grounded in the package source.
#Pick your path
No-code / app author — you live in the Filament admin and want to ship an app:
- Installation — get the panel plugin running.
- Architecture — the mental model in five minutes.
- Pages & components — build and publish pages.
- Collections & data — your own data tables.
- Flows — make things happen on clicks and data events (including atomic transaction + loop automations).
- Watchers — react to collection and state changes: run a flow when a record or a variable changes.
- AI — describe an app, review the plan, apply it, refine by chat.
Developer / integrator — you embed Synapse in a host app, extend it, or self-host its assets:
- Installation and Configuration — full env + config reference.
- Architecture — services, models, the request lifecycle.
- Functions & States — runtimes, the eval-free helper library, the reactive store.
- Authentication & permissions — the
pbguard, opt-in permission model, row-level rules. - Email — the isolated SMTP transport and templates.
- Extending — the overview: the capability-registry model, the
PageBuilderfacade, swapping models, theAiInvokercontract, observers. Sub-pages: Flows, Functions, Components.
#All pages
| Page | What it covers |
|---|---|
| installation.md | Requirements, composer require, plugin registration, publishing migrations/assets, optional AI gateway, env vars. |
| architecture.md | The seven pillars, "everything is data," and the request/AI lifecycle (with diagrams). |
| pages-and-components.md | GrapesJS builder, block vocabulary, per-page CSS/JS, the render route, home page, requires_auth, declarative Alpine binding, pbTable. |
| collections-and-data.md | Collections → pb_<key> tables, field types, the auto REST API, the filter/sort/search/paginate syntax, schema sync. |
| flows.md | The flow engine: triggers, every node type and its config (including the atomic transaction + loop control-flow nodes), the searchable node drawer, FlowContext interpolation, the public run endpoint, cron. |
| watchers.md | Reactive triggers: bind a collection event (created/updated/deleted, with criteria + changed-field conditions) or a state change (server or live-browser, with path/transition/operator conditions) to a target flow/function; test-fire, runs, export/import, and how they replace flow trigger_type. |
| functions-and-states.md | Functions (expression / callable / PHP) and the eval-free db.* / ui.* / auth.* / util.* helper library; States (the persistent reactive store). |
| authentication-and-permissions.md | The built app's users/roles/permissions, the pb guard, opt-in gating, row-level rules, component visibility. |
| email.md | SMTP settings, the isolated transport, email-template pages, the send_email node, mustache interpolation, send-test. |
| cloud-storage.md | Offload media to S3 / Azure Blob / GCS: the Settings → Storage tab, encrypted credentials, the pb-cloud runtime disk, and the migrate-media command (filesystem → cloud, with content URL rewriting). |
| ai.md | The Build Plan contract, "Build with AI," the floating chat, idempotent apply, the code-generated system prompt, safety. |
| configuration.md | A table of every key in config/ai-page-builder.php, with env var, default and meaning. |
| extending.md | Extending overview: the capability-registry model, the PageBuilder facade, swapping models, the AiInvoker contract, events/observers. |
| extending-flows.md | Flows — register a custom flow node (PageBuilder::registerNode), output handles, the capability catalogue, MCP/AI exposure (ai-page-builder:capabilities). |
| extending-functions.md | Functions — register a custom helper (PageBuilder::registerHelper), the expression sandbox + "Insert helper" dropdown, the callable-FunctionRegistry path, MCP/AI exposure. |
| extending-components.md | Components — register a custom/premium draggable block (PageBuilder::registerComponent), the Sections-category AI-vocabulary nuance, open-core premium component packs. |
#Conventions used in these docs
- Collection = a user-defined data model (a real DB table named
pb_<key>). - State = a persistent, app-wide global variable (the reactive store; the Filament resource is labelled "States," the model is
Variable). - Flow = an automation graph; Function = a reusable unit of logic a flow can call.
- Built app vs host app: the host is your Laravel application; the built app is what you author with Synapse (its pages, data and its own
pb-guard users).
The author
Hi, I'm Andre. Almost everything I've learned as a developer came from people who shared freely — open source, late-night forum answers, strangers who took the time to help. I owe a lot to this community. So I'm releasing free tools for anyone who needs them, hoping to give back even a fraction of what I've received.
From the same author
Featured Plugins
A selection of plugins curated by the Filament team
Blueprint
Filament Blueprint is a premium Laravel Boost extension that helps AI agents produce accurate, detailed implementation plans and security reports for Filament apps.
Filament
Custom Dashboards
Let your users build and share their own dashboards with a drag-and-drop interface. Define your data sources in PHP and let them do the rest.
Filament
Custom Fields
Eliminate custom field migrations forever. Let your users create and manage form fields directly in Filament admin panels with 20+ built-in field types, validation, and zero database changes.
Relaticle
