> ## Documentation Index
> Fetch the complete documentation index at: https://flexforms.bjanczak.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Write for Filament/Laravel developers buying Flex Forms.
> Be precise: every setting documents what it does and how it works.
> Use Help Center components richly: Steps, Cards, Callouts, Tabs, CodeGroup, Mermaid, Badge for Pro.
> Never invent APIs; match the real Flex Forms package behavior.

# How Flex Forms fits together

> Product architecture for builders — Studio, fill, submissions, Insights, and license checks.

This page explains how the **product** works inside your Filament app. It is for teams shipping forms — not for packaging internals.

<img src="https://mintcdn.com/flex-forms/GLPmjpfm86dAs3-u/images/tiles/architecture.webp?fit=max&auto=format&n=GLPmjpfm86dAs3-u&q=85&s=f3b2b6e152ab5f73053adc168742f5be" alt="Flex Forms architecture — Studio, fill, Insights, and license checks" width="680" height="404" data-path="images/tiles/architecture.webp" />

## Big picture

```mermaid theme={}
flowchart TB
  subgraph panel [Filament_panel]
    Studio[Studio_builder]
    Settings[Form_and_global_settings]
    Inbox[Submissions_inbox]
    InsightsUI[Insights]
    Contacts[Contacts]
  end

  subgraph public [Public_surface]
    Fill[Fill_pages]
    Embed[Embed_widget]
    ShareInsights[Shared_Insights_links]
  end

  Studio -->|publish| Fill
  Studio --> Embed
  Fill --> Inbox
  Fill --> InsightsUI
  Fill --> Contacts
  InsightsUI --> ShareInsights
  Settings --> Studio
  Settings --> Fill
```

## Studio → publish → fill

1. You design pages and fields in **Studio** (draft schema).
2. **Publish** promotes the schema so public fill routes use it.
3. Respondents open the **fill link** or an **embed**; answers become **submissions**.
4. **Insights** aggregates visits, answers, and drop-offs; **Contacts** consolidates respondents.

```mermaid theme={}
sequenceDiagram
  participant Admin
  participant Studio
  participant Fill as Public_fill
  participant DB as Database
  Admin->>Studio: Drag_fields_and_logic
  Admin->>Studio: Publish
  Fill->>DB: Submission_and_events
  Admin->>Studio: Read_Insights_and_inbox
```

## Why this architecture

| Surface | What you get |
| - | - |
| Studio | Canvas + left field settings + Logic / calculated / design — autosaves drafts |
| Form hub | Insights · Submissions · Share · Integrations — ops without leaving Filament. Form settings open from Studio as a modal. |
| Fill / embed | Dedicated runtime assets (not panel bloat), access gates, CAPTCHA, partials |
| Insights | Beacon → today buffer → rollups; optional Redis for uniques under load |
| License | Hostname + public key checked at runtime before Studio mutations and live submits |

That split is intentional: **builders** stay in Studio, **operators** stay in the hub, **respondents** hit a lean fill surface, and **your DB** remains the source of truth.

## Insights path (high level)

```mermaid theme={}
flowchart LR
  Fill[Fill_embed] --> Beacon[Analytics_beacon]
  Beacon --> Today[Today_buffer]
  Today --> Events[(Raw_events)]
  Today --> Redis[(Optional_Redis)]
  Events --> Rollup[Daily_rollup_job]
  Rollup --> Daily[(Daily_tables)]
  Redis --> UI[Insights_UI]
  Daily --> UI
  UI --> Share[Public_share_links]
```

Beacons from fill feed a today buffer (optionally Redis), then daily rollups power Answers / Visits / Drop-offs. Details: [Insights pipeline](/architecture/insights-pipeline) and [Redis scaling](/features/insights/redis-scaling).

## License gate (runtime)

On each request Flex Forms checks whether this hostname is allowed for your public key. Allowed apps get the full product; denied apps cannot mutate Studio data or accept live submissions.

See [Activate license](/get-started/activate-license) and [License flow](/architecture/license-flow).

## Where to go next

<CardGroup cols={2}>
  <Card title="Studio" icon="pencil-ruler" href="/features/studio/overview">
    Builder, logic, design, publish.
  </Card>

  <Card title="Embed API" icon="code-xml" href="/developers/embed-api">
    Drop forms on any website.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/developers/webhooks">
    Push submissions to your stack.
  </Card>

  <Card title="Extensibility" icon="puzzle" href="/developers/extensibility-overview">
    Events, FieldMapper, custom integrations, Connections, actions.
  </Card>

  <Card title="Config & env" icon="settings" href="/developers/config-env">
    Optional published configuration.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.