Platform

Build

Connect & extend

Govern & run

Government
EnterprisePricing
Resources

Live sessions

Platform · Forms

Forms that work like applications.

55+ field types, logic that runs in the browser and on the server, and the full action library behind every button, with security the browser can't bypass.

Illustration of the Plant an App form builder: a field palette, a funding request form on the canvas, and the settings of a State field that is visible only when the country is the United States.

Build

Describe it. Then shape it.

Start from a sentence and get a working draft. Then refine every detail on a visual canvas. Nothing about the draft is locked in.

  • A first draft in moments.

    Describe the form in plain language, and AI proposes the fields to start from.

  • Layouts that fit the content.

    Stack fields, line them up in rows, or place them freely on a grid, and nest containers for sections within sections.

  • Previewed before anyone sees it.

    Check the form at phone, tablet, and desktop widths, and in every language it supports.

Collect

Every kind of input, built in.

From a single text box to a signature, the field someone needs is already there, each with its own settings, validation, and output.

  • Everyday

    Text, rich text, numbers, money, phone, email, dates, and times

  • Choices

    Dropdowns, checkboxes, radio buttons, tags, sortable lists, tree pickers, star ratings, and sliders

  • Files & images

    Single and multi-file upload, a file manager, and an image editor

  • Location

    Countries and regions, address lookup, and maps that center on where the person is

  • Identity & security

    Passwords, CAPTCHA, device fingerprinting, and signatures

  • Structure

    Layout containers, repeaters, dynamic containers, content blocks, and buttons

React

Forms that adapt to every answer.

Everyone sees only what applies to them. The form responds as people type, and the server decides what exists at all.

Visible Browser

fields.Country.value === "United States"

Value Browser

fields.Price.value * fields.Quantity.value

Active Server

[HasRole:Reviewer]
  • Reactive.

    Fields appear, lock, or calculate their value as people type. Each rule tracks the fields it depends on. Nothing to wire by hand.

  • Dynamic.

    Fields can be added while the form runs, from data or earlier answers. Repeaters take as many rows as the work needs, and report which were added, changed, or removed.

  • Decided on the server.

    Server-side rules settle which fields exist for each person. A field that isn't active never reaches the browser.

Guide

Long forms, finished.

A form nobody completes has failed. Long processes become steps people can follow, and work in progress is never lost.

  • One step at a time.

    Long forms become steps people can follow, with logic that runs as they enter or leave each one, and errors flagged where they happen.

  • Nothing lost.

    Work in progress saves automatically, so people can pick up where they left off.

  • Drafts, your way.

    Need drafts kept on the server, handed to a colleague, or reviewed before submission? Actions shape the draft flow around the process.

Connect

Pre-filled, cascading, connected.

Nobody retypes what the organization already knows.

  • Open a record, get a filled form.

    An existing record loads straight into the form, ready to review or change.

  • Choices from real data.

    Lists come from entities, SQL queries, or external services, and filter each other as people choose.

  • Defaults that know the person.

    Default values can come from the signed-in user, the page, or any data source.

Act

Every button runs a workflow.

Submitting is only the beginning. Behind every button sits the platform's full action library, so one click can save, calculate, notify, generate, charge, and hand off.

  • The whole action library, one click away.

    Save to entities, call APIs, send email and SMS, generate PDF and Word documents, or run a workflow for each uploaded file.

  • Pause, confirm, continue.

    Actions can stop for a confirmation or a payment, then pick up exactly where they left off.

  • Progress as it happens.

    Results stream back to the person while the actions run.

Growing with every add-on and integration

Payment gateways
Stripe · PayPal · Authorize.Net
CRMs
Salesforce · Dynamics 365
Messaging
Email · SMS · Slack · Teams
Documents
PDF · Word · Excel
Automation
UiPath

No connector? Anything with an API works. SAP, for example, has been integrated in customer projects through its APIs.

Trust

Security the browser can't bypass.

Forms are where the outside world touches your systems. Every one is built to hold up, by design and not by configuration.

  • Bad or tampered data

    Input is checked as people type, then checked again on the server. Anything the rules don't allow is ignored, however the page was changed.

  • Exposed data

    Fields a person isn't allowed to see never reach their browser, and passwords are never sent back.

  • Forged submissions

    Every submission is verified as genuine, and the form is tied to the person filling it in.

  • Malicious input

    Text and rich content are cleaned before they're saved or shown.

  • Bots and abuse

    CAPTCHA, invisible risk scoring, and device fingerprinting keep automated submissions out.

  • Strict security policies

    Forms run under the strict browser policies security teams set, with no exceptions to carve out.

What reaches your datais what your rules allow.

Reach

Anywhere, in any language.

The same form works on a phone at the counter and a desktop in the office, in the language of whoever is filling it in.

  • Every screen.

    Layouts collapse to a single column on small screens, so forms stay usable on any device.

  • Every language.

    Translations use standard gettext files. Money, phone numbers, and dates follow each locale, and phone fields can detect the country.

  • Everywhere it's needed.

    Show a form inline, in a popup, or as a slide-in panel, or open it from anywhere with one JavaScript call.

55+

field types

20+

validators

450+

actions behind every button

2

layers of logic: browser and server

Start with the form your process depends on.

Talk to us about the intake, application, or request that needs more than a form builder, and see it built.