Platform
Skip the toolkit assembly. Data, interface, automation, APIs, access, and operations ship as one platform — every layer reads the same app definition.
Typed data definitions describe your application data once. The platform creates tables, runs upgrades, and provides one query layer shared by screens, automations, and APIs.
Screens are layout definitions — lists, detail views, forms, navigation — rendered by the platform and connected directly to your data and automation actions.
A visual workflow engine runs your logic: validations, writes, notifications, outbound calls. Automations are durable — they checkpoint, resume, and run on schedules.
Expose documented HTTP endpoints over the same queries and automations. Call external systems through scoped, managed credentials.
Permissions, reviews, and releases govern who can build, approve, and publish. Draft → validate → preview → review → publish is the lifecycle we are finishing.
Self-hostable from day one — run Floyant on infrastructure you control, on your own domain. Environments isolate drafts, previews, and live apps; scheduling, retention, and limits are declared in the app definition.
One model
Related data, screens, automations, and endpoints live in one app definition, so references can be inspected and changes reviewed together. That is what "platform" means here — one vocabulary across every layer.
data: monthly_summary
| period | region | total | delta |
|---|---|---|---|
| 2025-09 | EMEA | 48,210 | +6.1% |
| 2025-09 | AMER | 61,004 | +2.4% |
| 2025-08 | APAC | 22,730 | -1.2% |
automation · resumable · schedulable
Overview dashboard
Drill-down table
Export
screens · connected to data and automations