Getting started
Your first build, the editor, and what credits cover.
Answers to the questions that come up most, plus the paths to reach a person.
Your first build, the editor, and what credits cover.
Connecting a domain, SSL, DNS and going live.
Tables, submissions, exports and webhooks.
Plans, invoices, upgrades and cancellation.
Seats, roles, client access and SSO.
When a page will not publish or a form stops arriving.
Certificates are issued once DNS resolves to iPageForge, which can take up to an hour after you change records. If the warning persists beyond that, check that you have no conflicting AAAA record and that CAA records, if present, permit the issuing authority.
Submissions are always written to your project database first, so check the table before the email path — the entries are usually there. Missing email normally means the notification address bounced or the sending domain lost its DNS authentication records.
That is usually a cached preview. Use the version panel to confirm which revision is current, then republish. If the live site is correct and only the editor is stale, a hard refresh resolves it.
Published sites keep serving normally — credits only gate new generation. You can top up, upgrade mid-cycle and pay the prorated difference, or continue editing manually, which costs nothing.
Project transfer is available from project settings. The receiving account needs a plan with a free site slot. Domains, data tables and version history move with the project.
Yes, on every plan including Free. The export is a structured project — components, styles and the data schema — rather than a folder of rendered pages.
Support is part of every plan. Paid plans get a response within one business day; Agency plans within four hours.
This is a local design study — the contact routes above are not connected to a real support desk.
A polished, fully functional site in minutes — no code, no plugins, no hosting to configure.
Get Started