We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
For Creatives
For writers, designers, photographers and illustrators who work on their own. The work itself is yours to make; Ever Works takes on the part around it — the site, the deploys, the schedule, a memory of how you sound — and an Agent that minds it between projects. Every file lands in your own Git, so the site stays yours whatever you use next.
Three kinds of Work fit a solo practice. Each has its own repositories, deploy and schedule — start with one and add the others when you need them.
A Website Work built on the general-purpose Website template: a Next.js site with a hero, feature sections, testimonials, an FAQ, About and Contact pages and a Markdown blog. Prefer a static build with no JavaScript by default? Website (Minimal) is the same set of sections on Astro. Choose deliberately — the template locks after the first generation.
A Blog Work — in the product’s own words, a blog with categories, RSS, code highlighting and SEO-ready content. Posts get their own tab, categories and tags organize them, and a schedule from hourly to monthly keeps the runs coming. Today the Posts tab is filled by the platform’s shared content pipeline; a dedicated blog-post writer is rolling out.
Process notes, technique write-ups, reading lists, the vocabulary of your craft. Load them into a Work’s Memory tab — PDF, Word, PowerPoint and HTML are converted to Markdown as they arrive — ask questions of them and get answers with citations, then publish the notebook as a Website or Blog Work built from that knowledge. Readers of a Blog Work can follow it by RSS, and the Content Marketer Agent preset drafts newsletter issues from your notes for you to review.
Deploy to managed hosting on Ever Works and the Work gets an address of its own on ever.works; deploy to your own Vercel project or Kubernetes cluster instead if you already have one. A custom domain works on all three: add it, and the Deploy tab hands you the exact DNS record to create, then verifies it.
Four moves in the dashboard, each one leaving something you can read in Git afterwards.
Press + New in the sidebar, pick the Website or Blog chip and say what the site is for — “a portfolio for an illustrator who draws children’s books, quiet and warm”. Name the Work, choose the template and where it deploys in the same form, and press Create.
On Templates, Create with AI copies the Website or Website (Minimal) base into a new repository in your GitHub account and has a code-edit agent apply your design brief — colour, type, spacing, the feel of the cards. It is styling only; new features are out of scope. Customize again runs another round as a new commit. You need a code-edit plugin installed first.
Open the Work’s Memory tab and write down how you sound: a voice document, the words you never use, the projects you want mentioned and the ones you do not. Agents read it on every run. Lock a document and no run can rewrite it, or set it to additions-only so an Agent may append research but never change what you wrote.
Deploy from the Deploy tab, add your domain, and once the first generation has completed, arm a schedule on the Worker tab. Then hire a Work-scoped Agent — a Copywriter from the starter catalog suits most practices — and what it changes arrives as a pull request you merge, until you decide otherwise.
Ever Works is plain about which half of the job it does today. The site, the repositories, the deploys, the domain, the schedule and the Agents are all live. The words are further behind: the general-purpose Website template keeps its page copy in one site config file, and the platform does not write that copy for you yet — you edit the file, or hand it to your Agent as a Task, while dedicated page-copy and blog-post writers roll out. For most creators that is the right split anyway: the voice stays yours, and the upkeep does not have to.