Skip to content
Floyant

Features

Capabilities of the platform.

Data, screens, automation, and APIs already run underneath; the editing and release tools around them are being finished. Nothing here is claimed beyond that.

AI co-building

Describe the application you want and let AI draft the data, screens, and automations — then refine every piece directly.

  • Start from a description instead of a blank canvas
  • Every AI draft lands as an editable app definition you fully own
  • Switch freely between AI, visual, and file editing
Read more →

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.

  • Visual editors for screens, automations, and data models
  • Text files are human-readable and reviewable in version control
  • Free to move between editing styles at any time
Read more →

Data and storage

Model your business data as typed records. The platform creates storage, relationships, and queries from the same definitions.

  • Tables created from your data model
  • Typed fields, relationships, and rules declared once
  • One query layer shared by screens, automations, and APIs
Read more →

Pages and forms

Compose screens from a layout system — lists, detail views, forms, and navigation connected directly to your data and automations.

  • Screens are defined as data, so they are consistent and generatable
  • Components connect to your data, queries, and automation actions
  • Forms carry validation, state, and submission wiring in the definition
Read more →

Workflows and automation

A visual workflow engine runs your business logic — approvals, enrichment, notifications, scheduled jobs — as inspectable, resumable pipelines.

  • Built-in steps for branching, data, storage, and HTTP calls
  • Automations keep their state and are designed to resume after interruption
  • Schedules turn automations into recurring jobs without cron scripts
Read more →

APIs and integrations

Expose your app over versioned, documented HTTP APIs, and call external services through credential-managed outbound requests.

  • API definitions map endpoints to queries and automations
  • Outbound HTTP calls run inside automations with managed credentials
  • Credentials are scoped per account or workspace
Read more →

Governance and releases

Draft, validate, preview, review, and publish. Apps move through a deliberate lifecycle with one shared definition and versioned releases.

  • Draft changes without touching the live app
  • Validation catches broken connections before publish
  • Preview deployments give reviewers a real running app
Read more →

Hosting and operations

Self-hostable from day one: run Floyant on infrastructure you control. A managed hosted option is coming too — entirely optional.

  • Run on your own infrastructure — your servers, your domain, your rules
  • Environments isolate drafts, previews, and live apps
  • Self-hosting is a day-one capability — fully in your hands
Read more →