Say what the site is for
Who it serves and what it needs to do. The agent picks a structure and writes the first pass of copy — a starting point that argues with you, which is easier than a blank page.
Crafty · Consumer · Production · product site being redesigned
Describe the site. Then own it.
Most site builders give you a canvas and leave the hard part to you. Crafty starts from a sentence about what the site is for, produces something real to react to, and then gets out of the way so you can edit it directly. Behind that simplicity sits the rest of the job most builders leave out — an SEO engine, analytics, file storage and leads in the same admin — and publishing runs on our own CDN: on a subdomain to start with, on your own domain once you connect one.
01
How it goes
Four steps, and the third one is where most tools lose people.
Edit what you see
Text, images, sections and order are changed in place. Components come from one shared library, so a change to a button is a change everywhere — no page quietly left behind.
One step to live
The site is rendered to static files and pushed to object storage behind a CDN. Nothing is rendered on demand, so there is no server to fall over on the day traffic arrives.
Your domain, your content
Custom domains with certificates handled for you. Basic analytics and a newsletter capture are included rather than sold as an upgrade.
02
What is in it
The parts that exist today, in production, on customer sites.
- Templates
- Seven starting points — portfolio, agency, landing, retreat, static and others — as structure, not as a cage.
- Component library
- One definition per component, shared across every site. Fixing it once fixes it everywhere.
- Bring an existing site
- Drag in a folder of HTML and it becomes a managed site, keeping the markup you already have.
- Static delivery
- Pre-rendered pages on a CDN. Fast by construction rather than by optimization afterwards.
- Analytics and newsletter
- Page views and signups collected without adding a third-party tracker to your visitors.
- Assets
- Uploads go straight to storage from the browser, so large images do not travel through us.
03
The same stack, whatever the site is
There is no lite tier that quietly gives you worse infrastructure.
One architecture
A personal page and a company site are served the same way, from the same pipeline. Paying more buys scope, never a better foundation.
Pay once, not monthly
We chose one-time payments over subscriptions. Nothing you built stops working because a recurring charge failed while you were away.
Static output, no lock-in
What gets published is ordinary HTML, CSS and images on your domain. If you leave, the site keeps working somewhere else.
04
Honest boundaries
Where Crafty stops. Better to read it here than to discover it later.
It is not a design studio
For a considered brand system with custom illustration and motion work, hire people who do that. Crafty is for getting a clear, fast, well-built site standing without that budget.
Generated copy is a draft
The first pass of text is a starting point, not final wording. Anything with a legal or medical consequence needs a human to read it before it ships.
Onboarding is still by request
Self-serve signup and billing are being finished properly before they open. Until then access is granted directly, which is slower for us and honest for you.
Sites, not applications
Crafty publishes content sites with forms and analytics. It does not build a product with accounts, dashboards and a database behind it — that is a different job.
05
Questions about Crafty
The four that decide whether this is for you.
- Who owns what gets built?
- You do, from the first day. We build the tools and you own everything you create — full ownership of the result, with no strings and no fine print.
- Is it a subscription?
- No. Every payment is one-time, so there is nothing to cancel and nothing you built stops working because a recurring charge failed while you were away.
- What happens if I leave?
- What was published is ordinary HTML, CSS and images on your own domain. It keeps working without us, which is the point of publishing static output rather than renting you a viewer.
- Where does it run?
- Cloud-agnostic by design, running on Amazon Web Services today. The infrastructure is defined as code, so the choice of provider is a decision rather than a dependency.
- Can I sign up on my own?
- Not yet. Onboarding is by request today, because billing and self-serve signup are being finished properly before they open rather than patched together to look ready.