FormAssembly Custom Domains: Plans, Costs & Limitations [2026]

Quick answer: Yes. FormAssembly supports custom domains—your form links can go from yourinstance.tfaforms.net/123456 to forms.companyname.com/123456. But the feature is restricted to Team plan customers and higher, and per FormAssembly’s documentation, adding one means contacting your Customer Success Manager or sales representative—there’s no self-serve DNS flow. Note what stays in the URL: the form ID (123456 in the example above). Masking that too requires FormAssembly’s separate custom URL feature, which is documented apart from custom domains. And there’s no published price for any of it: FormAssembly’s plan matrix lists features, not prices, and the platform has no free plan—the entry point is a trial request or a demo.

In this guide, we’ll walk through what custom domains do on FormAssembly, how the documented setup works, what’s known—and not known—about cost, and the limitations worth knowing before you commit.

Yes—on Team and higher. Per FormAssembly’s documentation, custom domains let you replace the domain portion of your form links. The before and after:

Before:  yourinstance.tfaforms.net/123456
After:   forms.companyname.com/123456

FormAssembly’s own wording is worth noting: custom domains “mask the domain portion of your form links.” The domain your respondents see becomes yours; the form itself is still a FormAssembly form, served by FormAssembly’s platform.

Here’s the landscape:

The plan gate is confirmed from two directions: the requirements documentation (“custom domains are only available to Team plan customers and higher”) and the published plan matrix, which lists “Custom (Sub) Domain Choice” as ❌ on Atlas Explorer and ✅ on Atlas Team, Atlas Enterprise, and Gov Cloud.

Two structural details sit underneath the feature:

• The form ID persists. The documentation’s own example keeps /123456 after the domain swap. A shorter, memorable path mapped directly to a form isn’t part of the custom domain feature—FormAssembly handles that case with a separate custom URL feature.
• Setup runs through a person, not a DNS screen. There’s no documented add-domain-and-verify flow; the documented step is contacting your CSM or sales representative.

The custom domain changes the leftmost part of the link—the tfaforms.net portion with your instance name—and leaves the rest of the structure in place. The documentation’s example is explicit: forms.companyname.com/123456, “where 123456 is the form ID.”

So after connecting a custom domain, your links are branded at the domain but still carry the numeric form identifier—forms.companyname.com/123456, not forms.companyname.com/contact. For links in QR codes, print, ads, or email signatures, the brand improvement is real; the memorability improvement is partial.

The custom URL feature. FormAssembly’s documentation addresses the ID directly: “If you would like to mask the form ID as well you can use our custom URL feature.” That’s a separate feature from custom domains—documented apart from it—and the custom domain documentation doesn’t detail how it works or how the two interact. If the full package matters to your decision, the custom URL feature’s mechanics are a question to put to your CSM alongside the domain enablement.

The documented process is short, because it’s a conversation:

1. Be on Team or higher. Custom domains aren’t available on Atlas Explorer, the entry plan.
2. Contact your Customer Success Manager or sales representative to add the custom domain to your instance. If you need help reaching your CSM, FormAssembly’s documentation directs you to their Support Team—via email or a contact form.

That’s the extent of the public documentation. What isn’t published: the DNS records required, whether you add them before or after the request, verification steps, propagation expectations, and how SSL certificates are provisioned and renewed. None of that appears in the custom domain documentation—so before committing, those are the questions to ask in the sales conversation. For teams that prefer self-serve infrastructure—add a domain, add DNS records, watch for verification—FormAssembly’s flow starts with a person instead.

FormAssembly doesn’t publish plan prices on its plan matrix—the documented lineup is features, not dollars:

Three cost-relevant facts are visible in the matrix even without prices:

• The entry plan is excluded. Atlas Explorer—the plan a solo user would start on—doesn’t include custom domains. The feature first appears on Team.
• The tier jump is structural. Between Explorer and Team sit several gating features (unlimited workflows, document generation, custom HTML/CSS/JS)—so the path to a custom domain runs through a broader upgrade, not a single-feature line item.
• Integrations are add-ons at every tier. Even on Team and Enterprise, CRM, payments, and storage integrations are listed as add-ons—a plan-structure detail worth factoring into any total-cost comparison.

There’s also no free plan. FormAssembly’s entry point is a trial request or a booked demo—there’s no self-serve tier to evaluate the product on. To be fair to the positioning: this is a deliberate enterprise posture, not an oversight. FormAssembly serves compliance-heavy sectors—government (FedRAMP-authorized Gov Cloud), healthcare (HIPAA with BAA), and education (FERPA, Section 508, WCAG 2.1 accessibility)—and its plans include unlimited storage, forms, and responses at every tier, so usage isn’t metered either. The difference from self-serve platforms isn’t limits; it’s the front door.

• Team and higher. Custom domains aren’t available on Atlas Explorer. The published plan matrix confirms the gate.
• CSM- or sales-enabled, not self-serve. The documented setup step is contacting your Customer Success Manager or sales representative—there’s no documented DNS flow, verification process, or propagation guidance.
• The form ID stays in the URL by default. The documentation’s own example—forms.companyname.com/123456—keeps the numeric ID. Removing it requires the separate custom URL feature.
• The custom URL feature is documented separately. ID masking exists, but its mechanics aren’t part of the custom domain documentation—how it works, and how it combines with a custom domain, is a sales-conversation question.
• No published prices anywhere. The plan matrix lists features, not costs; the price of the plan that includes custom domains—and whether the domain feature itself carries additional cost—isn’t publicly documented.
• No free plan. Evaluation happens through a trial request or demo, not a self-serve tier.
• Subdomain-style examples only. The documentation’s examples are subdomain-based (forms.companyname.com); there’s no documented flow for apex (bare) domains.

What works well: FormAssembly’s documentation is unusually candid about the gate—stating the Team-plus requirement plainly and confirming it in the plan matrix with a dedicated row. Custom domains are included on Team, Enterprise, and Gov Cloud rather than sold as a per-domain add-on. And the platform’s unlimited usage across all plans, compliance certifications, and data-residency options are genuine strengths for the regulated sectors it targets. The friction is concentrated in what’s not documented: prices, DNS steps, and the custom URL feature’s mechanics.

The direct comparison, point by point:

Self-serve vs. CSM-gated. FormAssembly’s custom domain starts with your Customer Success Manager—no documented DNS flow, verification steps, or SSL details are public. Formware’s custom domains are a documented, self-serve feature on Pro at $29.99/month or $299/year: add the domain, add the DNS records Formware generates, and the domain moves from Pending Check to Verified as propagation completes—typically minutes to several hours.

Path mapping built in vs. a separate masking feature. On Formware, clean URLs are part of the domain feature itself: from the domain’s Configure screen, you map individual published forms to the paths you want—ask.acme.com/contact, ask.acme.com/customer-survey—and remove mappings with a trash icon. FormAssembly’s custom domain keeps the form ID in the URL by default, with ID masking handled by a separate custom URL feature whose mechanics aren’t publicly documented. For QR codes (or QR codes generated straight from your form), print, ads, and email signatures, a path you assign yourself beats an ID that needs a second feature to hide.

Published price vs. unpublished quote. Formware’s Pro pricing is on the website—$29.99/month or $299/year, the same for everyone, with custom domains included. FormAssembly’s plan matrix lists no prices, and its tiers gate a broader feature set, so the cost of reaching a custom domain isn’t publicly knowable.

The entry point. This is the sharpest difference in the series. FormAssembly has no free plan—evaluation starts with a trial request or a demo. Formware’s free plan is a fully usable platform: unlimited forms, questions, and responses (subject to fair use), alongside hidden fields (pair them with the UTM builder for campaign tracking), recall, and conditional logic at no cost. To be fair, FormAssembly’s paid plans don’t meter usage either—unlimited storage, forms, and responses appear on every tier. The difference is the door: a sales conversation versus a signup form.

Team structure. FormAssembly’s plans include 1 user on Explorer, 3 standard (plus 5 limited) on Team, and 5 standard (plus 10 limited) on Enterprise, with additional licenses available. Formware Pro includes unlimited team members with role-based access (Owner, Admin, Editor, Viewer) and multiple workspaces.

What surrounds the domain. On Formware Pro, the domain comes bundled with white-labeling—no “Powered by Formware” badge, your logo and favicon—plus per-ending custom redirects that hand respondents off to a booking page or checkout, respondent email notifications, and WhatsApp capabilities (sharing, widgets, and forwarding responses) if WhatsApp is a lead channel for your business. Forms are customizable down to colors, fonts, buttons, and backgrounds, with a one-question-at-a-time experience built for conversion.

The fair framing: FormAssembly is an enterprise workflow platform—document generation, e-signatures, Salesforce integration, and compliance certifications (FedRAMP, HIPAA, FERPA, WCAG) are its center of gravity, and for regulated deployments those are reasons to choose it. If your requirement is branded form URLs on a published, self-serve price, that’s not what its plan structure is built around.

If you’re weighing Formware against FormAssembly more broadly—beyond just domains—we break down the full comparison in Formware vs. FormAssembly.

Yes. FormAssembly supports custom domains on Team plans and higher—URLs like forms.companyname.com/123456 instead of yourinstance.tfaforms.net/123456. The feature must be enabled by contacting your Customer Success Manager or sales representative; it isn’t self-serve, and it isn’t available on Atlas Explorer, the entry plan.

Team or higher. FormAssembly’s documentation states custom domains are only available to Team plan customers and higher, and the plan matrix confirms it: “Custom (Sub) Domain Choice” is excluded from Atlas Explorer and included on Atlas Team, Atlas Enterprise, and Gov Cloud.

There’s no published price. FormAssembly’s plan matrix lists features rather than prices, custom domains first appear on Team (a broader upgrade from Explorer, not a single-feature add-on), and whether the domain feature itself carries additional cost isn’t publicly documented. Formware, by comparison, includes custom domains on Pro at $29.99/month or $299/year—published pricing.

Per the documentation: be on Team or higher, then contact your Customer Success Manager or sales representative to add the custom domain to your instance. If you need help reaching your CSM, FormAssembly’s Support Team can assist via email or their contact form. The DNS records, verification steps, and SSL handling aren’t part of the public documentation—ask for those details during the sales conversation.

Not with the custom domain feature alone—the documentation’s example keeps the numeric form ID in the URL after the domain is connected. FormAssembly offers a separate custom URL feature for masking the form ID, documented apart from custom domains. Formware builds path mapping into its custom domain feature: you assign each form a clean path like ask.acme.com/contact directly from the domain’s Configure screen.

No. FormAssembly’s entry point is a trial request or a booked demo—there’s no self-serve free tier. Its paid plans include unlimited storage, forms, and responses, so the difference from self-serve platforms isn’t usage limits; it’s the front door. Formware offers a free plan with unlimited forms, questions, and responses (subject to fair use), so you can build and evaluate before paying anything.

That’s not part of the documented flow. FormAssembly’s custom domain examples are subdomain-based—forms.companyname.com—and no public setup process covers apex (bare) domains. Formware supports both: apex domains via A records and subdomains via CNAME on its custom domains feature.

That’s not documented publicly. The custom domain documentation covers the CSM enablement step but doesn’t describe certificate provisioning or renewal—confirm how HTTPS is handled for your instance before committing. Formware issues SSL certificates automatically after domain verification and renews them automatically, with no configuration.

Formware includes custom domains on Pro at $29.99/month or $299/year—published pricing, self-serve DNS setup with automatic verification, both apex domains and subdomains, automatic SSL issuance and renewal, and clean per-form URLs like ask.acme.com/contact built into the domain feature. Its free plan offers unlimited forms, questions, and responses, plus hidden fields, logic, and recall. See the full Formware vs. FormAssembly comparison.

FormAssembly’s custom domain features and plan details were verified at the time of writing and may change. Check FormAssembly’s site for current plan details before making a purchase decision.