Describe it with AI
State the workflow in plain language. AI drafts the data, screens, and automations as real definitions you can inspect and edit — works with Claude, Codex, or any AI agent.
Self-hosted app builder and automation platform.
Coming soon — early access waitlist
Turn your workflows into applications you control.
Build personal tools and business applications with connected data, screens, APIs, and automation. Run them on your own infrastructure.
Works alongside Claude Codex any AI agent · Self-hostable from day one
data: request
| id | type | requester | state |
|---|---|---|---|
| REQ-1042 | Equipment | a.okafor | in_review |
| REQ-1041 | Access | m.silva | approved |
| REQ-1039 | Travel | j.larsen | draft |
- 1 Validate request
- 2 Route to approver
- 3 Record decision
- 4 Notify requester
automation · resumable · schedulable
Request inbox
Request detail
Approval form
screens · connected to data and automations
The argument
Your workflows are already applications — Floyant makes them run like ones.
Every approval chain, onboarding checklist, and reconciliation routine has the anatomy of an app: data, states, actions, people. Until now, that meant a project — so most of it still runs on spreadsheets, inboxes, and scripts.
Floyant closes that gap. The workflow you describe becomes the app definition; screens, storage, APIs, and automation come from it.
Why Floyant
Your AI agent writes the app. Floyant runs it.
Coding agents like Claude or Codex can build a full custom application. Floyant gives it the platform underneath — storage, forms, APIs, scheduled automations, and credential handling already built and shared across every app.
Floyant works with the AI agent you already use — Claude, Codex, or your own. Compare directly →
Three paths, one app
Author the way you think. Everything lands in the same model.
Compose it visually
The visual editor works on the same app definition — lay out screens, wire automations, shape the data model without leaving the canvas.
Write it as text
Prefer text? App definitions are readable text files — reviewable like code and easy for AI agents to work with.
Capabilities
One platform, from data model to running app.
AI co-building
Describe the application you want and let AI draft the data, screens, and automations — then refine every piece directly.
Visual editing and text files
One app definition, three ways to edit it: the visual editor, readable text files, or AI. Changes stay in sync because every tool edits the same definition.
Data and storage
Model your business data as typed records. The platform creates storage, relationships, and queries from the same definitions.
Pages and forms
Compose screens from a layout system — lists, detail views, forms, and navigation connected directly to your data and automations.
Workflows and automation
A visual workflow engine runs your business logic — approvals, enrichment, notifications, scheduled jobs — as inspectable, resumable pipelines.
APIs and integrations
Expose your app over versioned, documented HTTP APIs, and call external services through credential-managed outbound requests.
Governance and releases
Draft, validate, preview, review, and publish. Apps move through a deliberate lifecycle with one shared definition and versioned releases.
Hosting and operations
Self-hostable from day one: run Floyant on infrastructure you control. A managed hosted option is coming too — entirely optional.
Lifecycle
Draft, validate, preview, review, publish.
Changes move through a deliberate lifecycle — nothing reaches the live app without an explicit publish. Versioned releases make the app definition itself recoverable.
- 1
Draft
- 2
Validate
- 3
Preview
- 4
Review
- 5
Publish
What people build
Personal tools. Business applications.
Example app concepts — each one yours to shape.
Personal
Task and project tracker
Plan projects, track tasks, and review progress in one place.
See details → PersonalPersonal CRM
Keep contacts, conversations, and next follow-ups together.
See details → BusinessApproval and request desk
Capture requests, route decisions, and track outcomes.
See details → BusinessReconciliation and exception console
Compare two systems and review discrepancies in a queue.
See details →Extensible by design
Custom capability runs as services you operate — not code you upload.
Your own services are connected as trusted integrations called over a documented interface. Your proprietary logic stays on your infrastructure; Floyant calls it as part of an automation.
For developersCalling your service (example)
POST /your-service/scoreRequest
{"requestId":"REQ-1042"} Who it's for
Platform & operations teams
Replace the queue of internal-tool requests with a governed way to ship them — approvals, reporting workspaces, exception queues.
Agencies & consultants
Deliver client systems as maintained applications instead of one-off projects — onboarding, portals, operational tooling.
Domain builders & ISVs
Build a product on an application backbone — data, screens, automations, APIs — and extend it with services you operate.
Individuals & personal builders
Turn your own projects — trackers, collections, follow-ups — into real apps on infrastructure you control.
Is Floyant available today?
Floyant is coming soon — join the waitlist and we will contact you when access opens. The core platform underneath — data storage, screen rendering, automation, APIs, scheduling, and connecting your own services — already runs; the visual editor, review and release workflow, and app lifecycle tooling are being finished for the first release.
Can I build personal tools, not just business apps?
Yes — the same supported model covers personal tools (trackers, collections, follow-ups) and business applications. Every app runs in the browser on any device — our example concepts are starting points you shape, not fixed templates.
Why not just use a coding agent like Claude or Codex?
A coding agent can build a full custom application — the difference is how much infrastructure you choose to assemble and maintain yourself. Floyant provides the shared platform underneath (storage, forms, APIs, scheduled automations, credential handling). See Why Floyant for the honest comparison — including when direct coding is the better fit.
Where do apps run?
On your infrastructure — Floyant is self-hostable from day one, so you can run it on your own servers and domain. A managed hosted option is also coming — entirely optional. Exact packaging and installation requirements will be published at release.
What kinds of applications is it for?
Repeatable data + interface + automation shapes: personal trackers and managers, approval and request desks, reporting workspaces, client onboarding, evidence and review processes, reconciliation and exception consoles. These are the shapes the platform is designed around.
Get early access.
We plan to invite teams in small batches. Tell us what you'd build — suitable design partners may be invited to collaborate more closely.