About

We build the form tool we always wanted.

Powerful enough for an ops team, simple enough for a solo founder, and honest about who owns the data.

Why we exist

Askery, Inc.started from a frustration most teams know well: form builders force a choice between “free but rigid” and “powerful but expensive and locked-in.” You start on a free tool, outgrow it the week you need real branching or a clean data export, and then discover the capable alternative gates the features you need behind its top tier - and exports your work in a shape only it can read.

We think the defensible middle is a workflow-first studio: strong conditional logic, real analytics, native versioning and AI authoring, with none of the premium gating and none of the spreadsheet feel. Build a form as fast as you can describe it, keep the logic legible as it grows, and leave with everything intact whenever you want.

Our principles

  • Portability is a product, not a promise. One canonical schema, lossless CSV and JSON export, signed webhooks. No proprietary format, no lock-in. Read the developer contract.
  • Observability over magic. Logic you can read as a flow, versions you can compare and restore, analytics you can trust. The AI drafts; you can always see and edit exactly what it produced.
  • Compliance-aware from day one. Multi-tenant and row-level-secured from the first migration, so governance is a setting rather than a rewrite. See our security model.
  • Honest pricing.The capabilities that matter aren't dangled behind the most expensive plan, and a successful campaign shouldn't trigger a surprise bill. See pricing.

How the product is built

The form schema is a single typed source of truth - the same contract the editor, validation and AI all read from. There is no second model to drift out of sync, which is what keeps export lossless and the AI's output editable rather than opaque.

The app is a server-rendered Next.js application backed by Postgres on Supabase. Tenant isolation is enforced in the database with row-level security rather than in application code, and every public submission flows through a single audited write path instead of direct table access. Generated drafts are produced against the canonical schema and re-validated server-side before anything is stored - we never trust the client. You can read the full data flow in the security overview and the developer docs.

The team

We're a small, senior team that cares more about build quality than headcount. We'd rather ship a coherent product slowly than a sprawling one quickly. We're not going to inflate the team page or quote funding figures here - when there's something real and verifiable to say, it will say it plainly.

Work with us

We hire builders who care about craft and durability. Open roles and how we interview live on the careers page. For partnerships, press or anything else, reach us at support@askery.app or via the contact page.