Turn Text or a Document Into a Form, an API, and a Document Template
Paste text with fields, or drop in a Word or PDF document. All three outputs are built together, the same way every time, on servers you control.
Genie Snap at a glance
- What goes in
- A text block with tagged fields such as
{{Email_eml_req}}, a tagged Word/PDF file, or (optionally) a short description that a language model turns into a text block. - What comes out
- A web form you can rearrange in the editor, a REST API for it, and a document template that keeps your file's original layout. Generated together, so they always match. Together they are called a workflow.
- Is it AI?
- No. Building the outputs uses fixed rules, so the same text always gives the same result. A model is used only if you ask it to draft the text.
- Also included
- Hosting for every form at its own link, a submissions dashboard, tasks and approvals, multi-party eSignature, single sign-on, webhooks and integrations, portals, and teams.
- Where it runs
- Your servers: on-premises, private or public cloud, or air-gapped. Windows Server with IIS and SQL Server, or the Windows Docker image. No GPU.
- What it costs
- Free to try online. Self-hosted licenses are annual and per database cluster, not per user: $2,500 to $15,000 a year. Details
Build From Text Start here
Write or paste text and put each field in {{ }}, or write plain text like “Call 800-327-4399” and fields are detected. Press Generate to get the form, API, and document. No account is needed to generate and preview.
Describe what you need. A model (hosted, or local such as Ollama) drafts a text block into the box above. You review and edit it, then press Generate. The model only writes the text; it never builds the form, API, or document.
Build From a File
Drop in a DOCX, DOT, RTF, or PDF that already has {{ }} tags, or use Upload and Auto Tag File to have fields tagged for you. You get the same three outputs: form, API, and document.
How It Works
Every path above ends in the same text block, and the text block is built into the outputs the same way every time, so business teams can create production workflows without a traditional software development project.
1. Input varies
Text you write, a tagged file, or a description. If you use a description, a language model drafts the text block. This is the only step where a model can be involved.
2. Text block always
Plain text with each field tagged, such as {{First_Name_req}}. You can read and edit it before anything is built.
3. Outputs repeatable
The form, API, and document template are built from the text block by fixed rules. No model, and no differences between runs or machines.
Tag Reference
Wrap each field in {{ }}. A suffix sets the field type. Add _req to make a field required.
| Type | Suffix | Example | Required |
|---|---|---|---|
| Text (default) | — | {{First_Name}} | {{First_Name_req}} |
| Date | _dte | {{Due_Date_dte}} | {{Due_Date_dte_req}} |
| Email address | _eml | {{Contact_Email_eml}} | {{Contact_Email_eml_req}} |
| Phone | _tel | {{Phone_tel}} | {{Phone_tel_req}} |
| Currency | _cur | {{Total_cur}} | {{Total_cur_req}} |
| URL | _url | {{Site_url}} | {{Site_url_req}} |
| Long text | _mem | {{Notes_mem}} | {{Notes_mem_req}} |
| Whole number | _num | {{Quantity_num}} | {{Quantity_num_req}} |
| Decimal | _dec | {{Weight_dec}} | {{Weight_dec_req}} |
Repeating lists: give up to 4 columns the same list name after a dot, e.g. {{ItemNumber_req.product}}, {{ItemName_req.product}}, {{ItemQuantity.product}}, {{ItemCost.product}}. Here product is the list name.
One API Shape for Every Workflow
Every generated workflow uses the same endpoints, the same Bearer-key authorization, and the same contract structure. Only the field names change.
Learn it once
Submissions use WebSubmissionGenie; document-only generation uses WebDocumentGenieGenerate. Integration code written for one workflow works for the next.
Edits don't break it
Each downloaded contract carries version identifiers, so an integration built before a form is edited keeps working after. No /v2/ migration.
Callable by tools and agents
The demos on this page call the same REST endpoints your systems, scripts, or an AI agent can call. Download any form's contract from the dashboard.
API reference → (opens in a new tab) · Postman collection (opens in a new tab)
Included in the Platform
Hosting, submission management, eSignature, and single sign-on ship with the form builder.
Hosting and Submission Management
- Every saved form has its own link, served by the platform. Share it by link, email, website, portal, or API.
- Each submission is stored in your database with its generated document, data, attachments, and version history.
- The dashboard shows each person the submissions, tasks, to-dos, and notifications for their teams.
- Assign tasks, request approval or more information, and pend, close, or reopen, with a full status and comment history.
- Notifications, a calendar, renewal reminders by email, and records retention rules with legal hold.
- Chain one submission into other forms, send emails and webhooks, and pull lookup lists from other systems.
eSignature
- Send one document, or several together as one envelope, to signers in a set order, with automatic reminders and an optional expiration date.
- Works on documents built here, or any PDF/Word file you drop in and place signer fields on.
- Signers sign in on every envelope (their organization's SSO or an emailed code), and the email must match the one the request was sent to.
- Each signer sees and completes only their own fields.
- Before signing, each signer reviews and accepts a consent disclosure covering their right to a paper copy and how to withdraw consent, or declines.
- Signers see the signing page, consent, and emails in their own language: English, Spanish, German, French, Italian, or Portuguese, with more added by your administrator. The audit log stays in English.
- A signed copy is saved at every step, plus an audit log with timestamps and IP addresses.
- The finished PDF is sealed with your organization's X.509 certificate, so any PDF viewer shows whether it has changed since signing. The seal carries a document ID that links it to the audit log.
- Signatures, initials, and stamps can be drawn or uploaded as an image. Everything is available through the API.
Single Sign-On (OpenID Connect)
- Microsoft Entra ID, Okta, Auth0, Keycloak, and AD FS.
- Any number of tenants or realms per site, matched to each organization by email domain.
- Everyone else signs in with an emailed one-time code, so outside people don't need an account with your identity provider.
- Signing in from the editor or Document Setup opens a small window, so unsaved work stays in place.
- Configured per self-hosted site, against your own identity provider. Included at every license tier.
Teams and permissions keep each group's forms and submissions separate. See 13 use cases →
How It Compares by Category
A form builder or an eSignature service covers one part of intake. A cloud form suite covers more, but only in its vendor's cloud, and an enterprise workflow platform covers it at platform scale and cost. Genie Snap covers the whole flow in one platform that you install on your own servers.
| Capability | Form builder or SDK | eSignature service | All-in-one cloud form suite | Enterprise workflow platform | Genie Snap |
|---|---|---|---|---|---|
| Form hosting | Usually placed inside an application you build and run | Signing pages, sometimes with simple web forms | Hosted forms on the vendor's cloud | Portal pages you configure, often with per-user or per-login fees for outside users | Every saved form has its own link, portal, and API, served by the platform |
| Submission storage and dashboard | Often a back end or admin app you set up separately | Tracks envelopes and signed documents rather than intake records | Stored on the vendor's cloud, often with storage or per-form limits | Strong record and case management | Every submission stored with its document, data, and history, in one dashboard |
| Tasks and approvals | Usually handled in another tool | Signing order and reminders | Approval steps | Full workflow and case management | Assign, approve, request information, pend, close, and reopen |
| Document generation | Usually a separate service | Agreement templates, often filled from another system | Included or an add-on | Often a separate module | A document template built with each form and filled from every submission |
| eSignature | Usually a separate service | The core product | Included in higher tiers | Usually through an integrated signing service | Sequential and multi-party, with an audit log, built in |
| Self-hosted or air-gapped | Varies by product | Usually cloud-hosted | Usually cloud only | Usually cloud; self-hosting is limited, partner-led, or costly | On-premises, your cloud, or fully air-gapped |
Category descriptions are general; individual products vary.
Running Offline
The builder and the runtime need no cloud service, GPU, or AI model. A self-hosted install works the same online, on your network, or fully air-gapped.
| Connection | Needed? | Can it stay inside your network? |
|---|---|---|
| Email (SMTP or SendGrid) | Required | Yes, with an internal SMTP relay. SendGrid needs internet access. |
| Single sign-on | Optional | Yes, with an on-premises identity provider such as Keycloak or AD FS. |
| Stripe (in-form payments) | Optional | No. Stripe needs internet access, which you can restrict to Stripe's hosts. |
| Language model (drafting text) | Optional | Yes, with a local model such as Ollama. |
Data at rest can be encrypted with SQL Server Transparent Data Encryption for the databases and encrypted storage for files.
This hosted site loads Google Analytics. Self-hosted installations don't include the analytics tag.
On-premises load test report (PDF) (opens in a new tab) · Security scan results → · Security and architecture →
Running It
An administrator sets up the install once. After that, the work happens in the dashboard, done by the people who manage each team.
Administrator: once, then yearly
- Install on Windows Server with IIS and SQL Server, or from the Windows Docker image.
- Connect email through SMTP or SendGrid, and add the certificate that seals signed documents.
- Optionally set up single sign-on, Stripe, and a language model.
- Apply the license, renew it each year, and install updates.
Team owners and members: in the dashboard
- Create teams, add members, and set their permissions.
- Generate, edit, activate, and share forms by link or portal.
- Add and revoke the team's API keys.
- Work submissions, tasks, approvals, and signature requests.
- Team owners can connect a Stripe account to collect payments on their team's forms.
People filling out or signing forms need only a browser. They sign in with their organization's single sign-on or an emailed code, with no account to set up. Publishing a form takes no web hosting or development knowledge.
Guides and Videos
Documentation
Generating workflows, the editor, rules, the API, eSignature, and integrations.
Pricing and Download
Published prices. Annual licenses are per database cluster, not per user. Single sign-on and updates are included at every tier.
| Option | Limits | Price |
|---|---|---|
| Online sandbox | For evaluation, not production. 50 forms, 2,000 stored submissions. SSO is self-hosted only. | Free |
| Trial license | 1 month on your own servers with higher limits, including load testing. Extendable on request. | Free |
| Partner Demo | For partners' demos and proofs of concept, not production. 25 forms, 10,000 submissions a year. | Free |
| Starter | 25 forms, 10,000 submissions a year, for your own organization. | $2,500 / yr |
| Professional | 200 forms, 100,000 submissions a year | $5,000 / yr |
| Enterprise | 400 forms, 200,000 submissions a year | $10,000 / yr |
| Enterprise Plus | Unlimited forms and submissions | $15,000 / yr |
- Submission limits count new submissions per license year and reset each year.
- At the limit, or if a license expires, new submissions stop. Everything else keeps working.
- Forms built in the sandbox, with their rules, documents, and API contracts, can be downloaded and uploaded into any self-hosted installation.
- Installation is done by your team or a partner. Pay by card or invoice. Partner program → · License terms →
The download asks for a business email only to keep out bots. It isn't added to marketing lists. The trial license arrives by email. Afterward, request a license; it drops in to replace the trial license on the same installation.
Common Questions
What does Genie Snap do?
Genie Snap builds intake processes from a description or a Word or PDF document. People fill out a web form, and each submission fills in your original document, ready for signature. Every submission is tracked and routed from one dashboard and available to your other systems through the form's API, with nothing else to buy or build. You install it on your own servers: on-premises, in your cloud, or fully air-gapped. The form, its REST API, and its document template are generated together, so they always match.
Do I need anything else to host forms or manage submissions?
No. Each saved form has its own link, served by the same platform, and can also be shared through a portal, email, your website, or the API. Every submission is stored in your database with its document, data, attachments, and version history, and your team reviews, assigns, approves, and closes it from the dashboard. No separate web app, submissions database, workflow tool, document service, eSignature service, or single sign-on broker is needed.
Does Genie Snap use AI?
Only if you want help writing the text block. An optional language model can draft it from a short description. The step that builds the form, API, and document does not use a model, so the same text always produces the same form, API, and document.
Where does it run?
On servers you control: on-premises, in a private or public cloud, or fully air-gapped. It runs on Windows Server with IIS and SQL Server, or from a Windows Docker image. No GPU is required.
Does it run on Linux?
No. It runs on Windows Server with IIS and SQL Server, or from the Windows Docker image. Teams whose infrastructure is mostly Linux can run it on a Windows Server virtual machine in the cloud or virtualization platform they already use. No GPU or cluster is needed.
What outside connections does it need?
Email is required, through SMTP or SendGrid. Stripe (for in-form payments) and single sign-on are optional. Email and single sign-on can stay inside your network with an internal SMTP relay and an on-premises identity provider. Stripe requires internet access.
Does editing a form break integrations built against it?
No. Every downloaded API contract carries its own version identifiers, so a contract integrated before an edit keeps working after the form is changed and republished.
What does an administrator need to do to run it?
Install it once on Windows Server with IIS and SQL Server, or from the Windows Docker image, connect email, and apply the license, renewed each year. Single sign-on, Stripe, and a language model are optional settings. Everything else, including forms, teams, permissions, API keys, submissions, and signatures, is handled in the dashboard by the people who manage each team, based on their team permissions. Publishing a form takes no web hosting or development knowledge.
How is it different from a form builder or form SDK?
A form builder or SDK typically gives you a form designer and a renderer to place inside an application you build and run, with storage and back-office tools often set up separately. Genie Snap publishes each form at its own link and includes the submission storage, dashboard, tasks, documents, and eSignature, so there is no application to build around it.
How is it different from an eSignature service?
An eSignature service focuses on sending documents for signature. Genie Snap includes sequential multi-party eSignature, but signing is one step in a larger flow: the form that collects the data, the document generated from it, the submission record, and the tasks and approvals around it all live in the same platform, installed on your own servers.
Are the electronic signatures legally valid?
Genie Snap is built to support the U.S. ESIGN Act and UETA. Each signer reviews and accepts a consent disclosure before signing, signs in with single sign-on or an emailed code tied to the email address the request was sent to, and every delivery, sign-in, view, and signature is recorded in an audit log with timestamps and IP addresses. The finished PDF is sealed with your organization's X.509 certificate, so changes after signing are detectable. Whether a particular document can be signed electronically depends on the document type and jurisdiction, so confirm the requirements for your use.
Can I collect signatures on documents that were not built in Genie Snap?
Yes. Drop a PDF or Word file into Document Setup. If it already has signature tags they are detected; if not, you drag signer fields onto the page. Several documents can be sent together as one envelope.
Can I host it for my clients or offer it under my own brand?
Yes. Each instance is multi-tenant, so an MSP or integrator can serve many clients from one install, with a Team for each client. White-label mode replaces the product name, logos, footer, and email text with your own, and you set the price you charge. Licensing is per instance, not per client or user, and hosting clients needs Professional or above.
What does it cost to run?
The infrastructure is small. The hosted Genie Snap online sandbox runs on two web servers and one database server on IONOS, with Wasabi object storage, for about $180 a month including Windows Server and SQL Server licensing, with no per-GB charges for data sent out. In a load test on a single 4-core, 16 GB virtual machine, below the documented minimum, it handled 100 concurrent users at about one submission a second, each creating a record and a 6-page PDF, with typical responses of 300–600 ms. Your own costs depend on your hosting provider and SQL Server edition.
How is it priced?
Annual licenses are per database cluster, not per user. Starter is $2,500 a year (25 forms, 10,000 submissions, for your own organization). Professional is $5,000 a year (200 forms, 100,000 submissions), Enterprise is $10,000 a year (400 forms, 200,000 submissions), and Enterprise Plus is $15,000 a year (unlimited). Single sign-on and updates are included at every tier. Partners get a free Partner Demo license for demos and proofs of concept.