Developers

Readable app definitions. Documented interfaces. A real boundary.

Floyant applications are structured documents — you can read them, diff them, and generate them. The formats below reflect where we are heading; details firm up during early access.

One app definition

An application is a set of structured files. Whether AI, the visual editor, or your own tooling wrote them, the platform runs the same thing.

app definition (excerpt)

id: request-desk
name: Request Desk
version: 0.1.0
requiresPlatform: ">=1.0.0 <2.0.0"
contributes:
  apis:
    - apis/requests.yaml
  automations:
    - automations/request.json
  pages:
    - pages/request.json
  menus:
    - menus/menu.json

data model (excerpt)

request:
  type: object
  required: [id, title, state]
  properties:
    id: { type: string, format: uuid }
    title: { type: string }
    state:
      type: string
      enum: [draft, in_review, approved, rejected]

Your own services

Custom capability runs as a service you operate, registered with the platform and called from automations over a documented interface. It is a trusted integration point — deliberately not uploaded code.

calling your service (example)

POST /your-service/scoreRequest
{"requestId":"REQ-1042"}

The function name is illustrative — the service must advertise and support it. Transport security, authentication, and registration are defined by the documented interface, not shown here.

· You run the service: your infra, your runtime, your release cycle
· The platform calls it with managed, scoped credentials
· Automations use it like any other step — inspectably

Working today vs. still being built

Working today

· Storage from your data model
· Structured queries
· Screen rendering
· Automation runs + scheduling
· Documented HTTP endpoints
· Calling your own services

Still being built

· Visual editor
· CLI / file-based workflow
· Documented formats
· Review & release lifecycle
· Preview deployments
· Self-hosted packaging & install docs
· External agent tooling guides

Readable definitions ≠ platform independence

Readable app definitions and documented interfaces mean you can inspect and generate everything the platform runs, and Floyant is self-hostable — you can run it on infrastructure you control. Self-hosting doesn't make app code portable to other platforms: the execution model remains Floyant's. We don't claim zero lock-in; we claim legibility and operational control.

Help define the formats

Early-access teams and invited design partners will see format drafts first and get a direct line to shape them. External agents are a complement — use a coding agent with Floyant, not instead of it (comparison).

Join waitlist