Your form admin panel.
Built in minutes, not months.
Four React components — a drag-and-drop form designer, a submission viewer, a theme editor and a clinical instrument set. Drop them into your app, keep your data, pay once.
Form administration is where side projects go to die
The form is the easy part. The panel around it — builder, responses, theming, exports — is the quarter you did not plan for.
- ×Drag-and-drop editing is three weeks before it feels right
- ×Undo/redo and keyboard support get cut from scope
- ×Response tables, filters and CSV export rebuilt per project
- ×You now maintain an internal product nobody asked for
- ×Per-response pricing that scales against you
- ×Submissions live in someone else’s database
- ×An iframe you cannot style to match your product
- ×Compliance review every time the vendor changes terms
- ✓A finished builder, viewer and theme editor as components
- ✓Runs in your app, against your database
- ✓$199 once — no per-response ceiling, ever
- ✓Built on the MIT-licensed engine you already use
Design the form, get the schema
Drag fields in, set conditions and validation, and export the same JSON your renderer already reads. This is the real component — try it.
Read the submissions without writing a table
Point it at your rows. Table, cards, detail and split views, search, filters, bulk actions and exports come with it.
Make it look like your product
Tune tokens against a live preview, then export CSS variables or a theme object. Five presets to start from.
Validated clinical instruments, already scored
PHQ-9, GAD-7 and PSS-10 as schemas with scoring, severity bands and subscale totals computed by the engine.
Pain scales, a body region selector, vitals with unit handling and reference ranges — as first-class field types.
Intake, screening and follow-up assessment schemas you can copy into your repository and edit like any other form.
45 features, one licence
One provider, then the components
Wrap your admin route in the provider with your licence key. Every Pro component reads it from context — no per-component config, no build step.
'use client' import { FieldCraftProProvider, FormBuilder } from '@squaredr/fieldcraft-pro' export default function FormsAdmin() { return ( <FieldCraftProProvider licenseKey={process.env.NEXT_PUBLIC_FC_KEY}> <FormBuilder schema={schema} onSave={(next) => saveSchema(next)} modules={['telehealth']} /> </FieldCraftProProvider> ) }
Buy it once. Ship it everywhere.
One licence per production domain. Unlimited development and staging use.
- ✓FormBuilder, ResponseViewer and ThemeEditor components
- ✓Telehealth module with scored clinical instruments
- ✓All 44 field types plus the Pro-only advanced set
- ✓TypeScript types and full API reference
- ✓Twelve months of updates, including new modules
- ✓Private issue tracker with maintainer response
- ✓Commercial use in client and internal projects
Before you ask
Licensing edge cases, roadmap, or whether the Telehealth module covers your instrument — ask. Replies come from the maintainer.