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.
Build the thing
A Work is a live site that Ever Works builds and then maintains: it researches the topic, writes the content, generates production-grade code, deploys it to your target, and keeps it refreshing on a schedule. Code and content both live in your own Git.
The five kinds you pick on the create screen — website, landing page, blog, directory and awesome repo — are each wired end to end: their own tabs, Overview tiles, per-kind works.yml spec, deploy target and schedule. The writer behind them is not equally deep yet: directories and awesome repos have the dedicated content generator, while website, blog and landing-page Works are written by that same items pipeline today and their kind-specific generators are rolling out. A knowledge base is not a separate kind — every Work carries one on its Memory tab.
Marketing and product sites, generated from the general web template and filled with researched content.
Posts that keep publishing on the cadence you set — written by the items pipeline today, with a dedicated blog-post generator rolling out.
Curated, filterable lists that find and add new items over time.
Single-purpose conversion pages, shipped fast — the web template supplies the sections while dedicated landing-copy generation rolls out.
Community-curated lists, kept current automatically.
Not a sixth kind — a surface each of the five carries on its Memory tab: searchable internal or external documentation every generation reads from.
Create with AI from a prompt, build manually with full control, or import an existing repo or list to bring it under management. Every Work is generated from a template so you are never starting from a blank page.
All five kinds are wired end to end: the chip on the create screen, the persisted kind, the per-kind capability registry, the tabs and Overview tiles, the works.yml spec, the deploy and the schedule. Where they differ is the writer. The directory and awesome-repo kinds have the dedicated content generator — it produces items and their markdown, categories, tags, collections, cited references and comparisons. Website, blog and landing-page Works run that same items pipeline today, so their Pages and Posts surfaces fill from it and the web template supplies the landing sections, while kind-specific page-copy and blog-post generation is rolling out.
Every Work is generated from a template — production-grade Next.js and Astro bases — so you never start from a blank page.
Learn more →One-shot builders generate a site and stop. Ever Works keeps researching, writing, building, and improving — on a schedule.
Learn more →Named AI employees — a CEO, a CTO, a Researcher — that run your Missions, Ideas, and Works around the clock.
Learn more →Build an online store as a Work — pick a storefront template, choose your backend, and let an AI team stock, write, and grow it.
Learn more →Point Ever Works at an open-source project on GitHub and it will build it, run it on your own Kubernetes cluster, and keep improving your copy — with the code in your own Git.
Learn more →Describe what you want to build. Ever Works researches it, ships it, and keeps it improving — content and code, owned in your own Git.