Compare with Carrd
Considering a Carrd alternative?
Carrd builds one-page sites whose forms pass entries to your inbox, a mailing tool or another service. See what its download keeps and leaves out, and when a page needs an app that stores entries and signs people in.
Carrd
Where Carrd fits.
Carrd builds responsive one-page sites for almost any purpose, from a personal profile to a landing page that captures emails. You start from a template or a blank page, and the site adjusts to phones, tablets and desktops. Pro plans add custom domains, forms, embeds and more.[1]
Sections in place of pages
Everything sits on one page. Sections divide it into named regions that links switch between, which Carrd's docs describe as simulating multiple pages. The same sections can also serve as menus or form confirmations.[2]
Forms that pass entries on
A contact form emails your account address or recipients you choose, and a signup form adds people to a mailing tool such as Mailchimp or Kit. Custom forms can also send entries to Zapier, Make, n8n, Airtable or a URL.[3][4][5]
Features by plan tier
Pro Lite, Pro Standard and Pro Plus are yearly plans. Standard adds custom domains, forms and embeds. Plus adds custom forms, payments, password protection, redirects and site downloads.[6]
Exepad
Where Exepad fits.
Exepad is Your App Cloud. Instead of arranging sections on one page, you describe the pages of a site or app in Studio, review them, and publish a web app that opens in a browser, including on phones. A page that only presents content can stay on Free, which puts one one-page site live. Keeping entries, signing people in and sending email make it an app, which needs a paid plan to go live.
Entries become records
The app can keep each form entry in its own database, with a list where you give it a status or a note instead of reading it in an inbox. Say which fields to keep, then send a test entry and find it.
Accounts instead of a site password
Where Carrd asks visitors for the username and password set on the site, an app lets each person sign in with an account of their own. Describe the access for each collection, then test it with an account that should see less.[7]
Confirmations and uploads
An app can email a confirmation after someone signs up and keep the files people attach in file storage. Test the message and a sample upload on a phone before anyone relies on them.
Compare the work you need to do.
| Consider | Carrd | Exepad |
|---|---|---|
| Page scope | One-page sites. Links switch between named sections to simulate several pages on the one page.[1][2] | The pages you describe in Studio. A public page can stay on Free. Add a sign-up form and an entries list that asks for sign-in, then test who can open it. |
| Where form entries go | Contact forms email your Carrd account address or other recipients. Signup forms add names and emails to a tool such as Mailchimp or Kit. Both need Pro Standard or higher.[3][4] | Into the app's own database. Say which fields each form keeps, then send a test entry and find it in the list. |
| Custom fields and hand-offs | Custom forms on Pro Plus combine field types, including file uploads, and send entries to email, Zapier, Make, n8n, an Airtable table or a URL.[5] | The form and the records it fills belong to one app. The app can keep attached files in file storage. Check that a test upload opens from its entry. |
| Keeping a page private | Password protection on Pro Plus asks visitors for the username and password you set on the site before they can view it.[7] | Authentication, so each person signs in with their own account instead of one password for the whole site. Describe the access for each collection before you send anyone the link. |
| Taking payments | On Pro Plus, a payment-enabled form puts a Stripe Checkout screen between submitting the form and processing it.[8] | Link the form to the checkout page you already use, such as your payment provider's own page, and record in the app who has paid. |
| Web address | Sites publish to .carrd.co URLs. A custom domain you have registered needs Pro Standard or higher and comes with SSL.[9][6] | Free publishes on an Exepad address. Custom domains are on Pro, so connect yours once the app has passed your checks. |
| Getting the site out | Pro Plus downloads a ZIP of the unminified HTML, CSS and JS. Forms are visible but don't work in it, and it can't be uploaded back to Carrd.[10] | You can export your app's data and code. Run an export and check that the stored entries are in it before you depend on it. |
| Other people who edit | Sharing, with the site owner on Pro Lite or higher, gives another Carrd user Admin, Editor or Template access to one site.[11] | Each Exepad account has one builder, who edits the site in Studio. Visitors who sign in to the published app are app users, a separate group. |
| How plans are charged | Yearly Pro plans in tiers set by features and number of site slots. Renew automatically or pay as you go.[12][13] | Free puts one one-page site live. Paid plans, for apps with saved data, sign-in or email, are priced per month rather than per year, and model and service usage is metered separately. |
Choose Carrd when
One page and one next step is the whole job.
A personal profile or a landing page that captures emails fits Carrd's one-page model, and sections can stand in for extra pages. If no one needs to work through the entries later, an app adds little.
New sign-ups belong in a mailing tool you already use.
A Carrd signup form sends names and emails straight to tools such as Mailchimp, Kit or MailerLite. If your newsletter is where people should end up, that hand-off is the job.
You run many small sites from one account.
Carrd plans are sized by site slots, and custom templates let you start similar sites from your own design instead of cloning one repeatedly. Sharing gives other people edit access site by site.
Choose Exepad when
Sign-ups have to become records someone works through.
Registrations, applications or requests need a status, a note and a reply, not only an email in your inbox. Describe an app that keeps them in a list with those fields, and decide who reviews each one.
Visitors need accounts of their own.
A members page, a client area or course notes need each person to sign in and see their own items. Describe that access for each collection, and test it with two accounts.
The page is growing into a small app.
The one page now needs a class list, a directory or a place for uploaded files. Describe those pages in Studio next to the public page, then review and publish them together.
What changes when you move from Carrd.
Carrd's docs describe one way to take a site with you: Download, on Pro Plus or higher, which prepares a ZIP of the site's source. Read what it holds before you plan the move.
What an export brings
- The site's source code. Unminified HTML, CSS and JS. Copy the text, headings and links you want to keep from the HTML.[10]
- Images. Carrd's plans page lists the site's images in the download along with its code.[6]
- One ZIP per site. Pick the site on the dashboard's Sites tab, open its Manage icon and choose Download, then Download Zip. Repeat for each site you move.[10]
What stays behind
- Working forms. Forms and other elements that need the Carrd platform stay visible in the download but don't function. Note where each form sends its entries today.[10]
- Server-side code. The plans page says the download excludes it. Plan to rebuild what the site does, not only how it looks.[6]
- A route back. A downloaded site can't be uploaded back to Carrd. Keep the original published until the new app passes your checks.[10]
- Earlier entries. Contact messages went to your account email or chosen recipients, and signups to your mailing tool. Gather earlier entries from there if the app should hold them.[3][4]
Rebuild it in Exepad
Bring the page's text and a screenshot
Paste the copy from the download or the live page, and attach a screenshot as a layout reference. Say which sections should become pages of their own.
Describe what each form keeps
For every Carrd form, name its fields, where entries are kept, who reviews them and what the sender sees after submitting.
Decide who signs in
If the Carrd site was password protected, decide who gets an account and what each person may open. Then check it by signing in as someone who should see less.
Test it on a phone
Open the published app on a phone, send a test entry through each form and check that any confirmation email arrives.
Move the domain last
Keep the Carrd site live until those checks pass, then connect your custom domain to the Exepad app on Pro.
Try it with one task.
Move the class sign-up section first
An illustrative pilot for Emma Clarke, a sample yoga teacher in Santa Barbara, California, whose Carrd page takes class sign-ups. Prove that one section before you rebuild the rest.
On Carrd, list the sign-up form's fields and where its entries go today, such as a Mailchimp audience.
In Studio, describe a class page with a form for name, email and class, and a sign-up list only Emma can open.
Ask for a confirmation email to each person who signs up, then sign up yourself as a test.
On a phone, submit three test sign-ups and check that each appears in the list under the right class.
Keep the Carrd page live until those checks pass, then decide when to move the domain.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Database
Keep data and context for apps and agents
Authentication
Give the right people access
Email
Keep conversations moving
File storage
A home for your documents and media
A little more context
Good questions.
Can I publish a one-page site on Exepad for free?
Yes, when the page shows content and links out, like a Carrd profile with no form: Free puts one one-page site live on an Exepad address. Storing sign-ups, signing visitors in or sending email makes it an app, which needs a paid plan to go live, and your own domain needs Pro. Compare the plans on the pricing page before you move a site with forms.
Does a Carrd download keep my forms working?
No. Carrd's docs say elements that need the Carrd platform, most notably forms, stay visible in the downloaded ZIP but don't work, and the download can't be uploaded back to Carrd. Treat the ZIP as a copy of your text and images, then rebuild each form and decide where its entries are kept.
When does a page like mine need a paid plan?
When it has to keep something or know who is visiting. On Carrd, forms, payments, password protection and custom domains sit on Pro Standard or Pro Plus. In Exepad, stored entries, sign-in and email run on a backend, which makes the page an app, and an app needs a paid plan to go live. Custom domains are Pro.
Can I start from a screenshot of my Carrd page?
Yes. Attach a screenshot as a reference for the layout and paste the page's text alongside it. A screenshot shows how the page looks, not what its forms do, so describe each form's fields and where entries should go. Then compare the result with your Carrd page on a phone.
Can I keep my domain when I leave Carrd?
Yes, on Pro, which includes custom domains. On Carrd, DNS records at your domain provider point the domain at the site. When the Exepad app has passed your checks, connect the domain to it instead, and keep the Carrd site published until then.
How do Carrd's yearly plans compare with Exepad's plans?
Carrd sells yearly Pro plans in tiers set by features and number of sites, and you can renew automatically or pay as you go. Exepad has a Free plan and monthly paid plans, with model and service usage metered separately. Compare the features your page actually uses rather than the plan names.
Can I export my site from Exepad if I move again?
Yes. You can export your app's data and code. A Carrd download leaves its forms inactive, so check the Exepad side the same way: run an export and confirm it holds your stored sign-ups as well as the pages before you rely on it for a move or a backup.
Explore Pricing for plans, included capabilities, and usage details.
Related guides.
Compare other tools.
Sources.
Carrd details checked September 25, 2026. Confirm them on Carrd's site before you decide.
- Carrd: product overview ↗
- Carrd: using sections ↗
- Carrd: setting up a contact form ↗
- Carrd: setting up a signup form ↗
- Carrd: setting up a custom form ↗
- Carrd: Pro plans ↗
- Carrd: adding password protection ↗
- Carrd: setting up a payment-enabled form ↗
- Carrd: using a custom domain ↗
- Carrd: downloading a site ↗
- Carrd: sharing access to a site ↗
- Carrd: Go Pro plan comparison ↗
- Carrd: understanding site slots ↗
- Carrd: working with custom templates ↗
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building