For web designers & freelancers

Your markup ships exactly as you wrote it.

You build the site in two days, then lose a week to plugins, form spam, a gateway and whichever CRM the client's cousin recommended. On a Custom page here, the HTML you save is what ships, with forms, checkout, CRM and A/B tests already behind it.

Start free

AXL Custom page Code view beside the rendered page, with matching studio-intro and data-build markers.

Edit the custom HTML and inspect the rendered result side by side.

What AXL replaces

One account you hand over, instead of five you keep supporting.

  • Your markup, untouched

    A Custom page stores your head and body HTML and ships both verbatim. Brand Style Kit presets drop --color-* and --font-* tokens into that head.

  • Forms and quizzes

    23 element types, 6 templates and a widget you can drop on any page. Branching questions included.

  • Checkout as a page element

    Multi-product, promo codes, an order bump and an inline Stripe card form.

  • A real CRM behind every form

    Each deal carries a “source” naming the site, page and form that produced it.

  • Where your own files live

    Head HTML is passthrough, so fonts, meta and analytics go there. CSS and JS upload to the site's Files tab, images to the media library.

  • Variation tests

    Shipped in the admin today. The statistics table sits in that page's own A/B tab.

Your first 90 minutes

Shell, pages, then the part clients actually pay for.

  1. 0 to 30

    The shell

    Create the site, then point the client's domain: add the A record AXL shows, tick “DNS settings applied”, confirm, and SSL issues itself. Until then it runs on a platform subdomain. Attach header and footer as shared components; attaching replaces the page set they sit on rather than adding to it.

  2. 30 to 60

    The pages

    Pages nest, and a page's URL is its parent's plus its own segment. Paste your HTML into a Custom page, or let the AI builder draft from a reference and hand-edit what it gets wrong. Save a draft and send the client a secret preview link: no login, and it renders noindex. Publishing is a separate switch. Every page keeps its last 100 revisions with revert.

  3. 60 to 90

    The part they pay for

    Wire the form to a pipeline stage, add a scenario that emails the client on each lead, start a variation test. Then hand over one login.

Five things worth knowing before you quote

  • Page templates are a read-only catalogue: you copy the markup, you do not apply one.
  • Every page loads one platform stylesheet of ~700 KB.
  • The pipeline emits no srcset and no WebP, so size images at upload.
  • Only images get a permanent public link. A PDF or a zip gets one that expires after six hours.
  • Platform utility classes carry only md: and lg:, and arbitrary values like text-[15px] are inert; your own CSS is untouched.
The AI shortcut

Draft five pages from a reference, then edit by hand.

You, to your agent

New site for my client on the brand style I just saved. Five pages from the outline below; home follows the structure (not the copy) of https://example.com/reference. A contact form on /contact creating a deal in “New leads”. Preview links, publish nothing.

Connect your own agent →

Questions

What designers ask before the first job.

No. On a Custom page the markup you save is the markup that ships, enforced in the renderer. One exception: a lead form and a checkout block are wired through literal class names, so style them freely but do not restructure them or attach your own JS, or they render without submitting. Custom pages and revisions →

Build a client site in AXL.

Nothing goes live until you publish. Plans start at $49 per month with included usage, and AXL takes 0% of your revenue or your client's.

Start free