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.
Compare · Company builders
Coding-agent board for your GitHub repos
Fredrin runs many coding agents in parallel against a GitHub repository you already have, and stops at the pull request. Ever Works starts from a topic — research, content, code, deploy — and keeps the site improving on a schedule, in your own Git.
Fredrin is a board for running many AI coding agents in parallel against GitHub repositories you already own. Every ticket gets its own branch, a real git worktree, its own agent session and its own dev server, and the agent’s final act runs that ticket’s acceptance checks — a red result opens no pull request, and by default nothing reaches your base branch until a human merges. Around the board sit Automations that dispatch a fresh agent run on an hourly, daily or weekly schedule, Reports an agent writes over the repository and connected data, and a reviewed, sandboxed marketplace of apps people built by describing them — the featured one being a search-traffic report — so calling it a mere task runner would be unfair. The boundary is what comes out the other end: it needs a repository that already exists, it generates no website content, and it publishes nothing — no researched items, no taxonomy, no deploy, no domains. Fredrin draws that line itself: its own comparison pages say the audience is developers with real repositories, not people who want an app generated for them. Ever Works starts earlier and finishes later: from a topic it researches the niche, writes the content, generates the site from a template, deploys it, and keeps re-running that loop on a schedule — with content and code committed to your Git under an AGPLv3 runtime you can host yourself.
This is the honest boundary between the two products, and it is worth stating before anything else. Fredrin begins where a GitHub repository already exists and a developer knows what should change in it; there is no path from "I want a directory about X" to a live site, because it researches no subject matter, writes no page content, builds no taxonomy, deploys nothing and manages no domains. Ever Works treats the published artifact as the deliverable: its pipeline researches the niche, writes items, categories, tags, collections, comparison pages and SEO metadata, generates the site from a template, and deploys it to Vercel or Kubernetes on your own domain. Where we are is worth being straight about too — the directory kind is the mature one, and Blog, Website and Landing Page Works are wired end to end but still fed by that same items pipeline; dedicated post and landing-copy writers are not there yet.
It would be wrong to say Fredrin has no scheduler: its Automations turn a saved prompt into recurring unattended dispatch, spawning a fresh ticket and an agent run on an hourly, daily or weekly cadence, and its Reports app has an agent write documents from the repository and connected data. What is scheduled there is a coding agent pointed at a repo, and what comes back is a pull request or an internal report. Ever Works schedules the content work: Scheduled Updates re-run the whole generation pipeline on one of seven cadences from hourly to monthly, with retries, failure tracking and automatic pausing after repeated failures, so new items appear, stale entries are refreshed, sources are re-validated, and the result lands as commits and a redeploy. Recurring Tasks on a Daily, Weekly, Monthly or custom recurrence rule and Agent heartbeats sit on top of that, as does Mission auto-build once the Work agent is switched on.
Fredrin keeps your code in your own GitHub repositories, which is a genuine ownership position — but GitHub is the only host it runs against, and neither GitLab nor a self-hosted Git server appears anywhere on its site. Ever Works asks where your repositories should live during setup and takes four answers: managed Ever Works Git, your own GitHub, your own GitLab, or your own self-hosted Git server. Everything around the repository differs too. Fredrin is closed source with no self-host path published anywhere on its site, and its own comparison against an Apache-2.0 rival concedes that it is not free and open source. Ever Works is plain AGPLv3 with no paid feature tier — every capability described here lives in a repository you can read, fork and run — self-hostable with Docker or Kubernetes, and it commits the content and the typed, per-Work Knowledge Base alongside the code rather than the code alone.
With Fredrin you write the tickets, and Goals group them so it can infer the order. Ever Works gives you Missions that keep proposing Ideas, Ideas that become Works, and a named, persistent Agent team with scopes, Skills, Teams, email inboxes and a spend cap enforced before each AI call rather than counted afterwards — wrapped in quality gates, approvals and escalations, and a merge policy resolved field by field across tenant, organization, Work and Agent. On the agent mechanics themselves the two products sit close together: Ever Works ships branch-and-checkout isolation (opt-in per Work, with a per-Task override), acceptance checks that send red work back to the Agent, a conflict state that names the conflicting paths, live agent terminals, and decision documents with a review queue. Being fair about the roadmap: the Store builder is planned, and company registration is a manual v1 today, with incorporation through formation providers still ahead of us.
Ever Works vs Fredrin, head to head.
| Feature | Ever Works | Fredrin |
|---|---|---|
| Prompt → working app/site | ✓ | Needs an existing repo |
| Researches the topic for you | ✓ | – |
| Writes the content (copy, posts, SEO) | Directory data today; posts not yet | Reports about the repo |
| Generated code from a template base | ✓ | Edits your repo |
| Deploys the site and manages domains | ✓ | – |
| Ongoing autonomous maintenance | Scheduled content runs | Scheduled dispatch |
| Branch + isolated checkout per task | Opt-in per Work | ✓ |
| Acceptance checks gate the pull request | ✓ | ✓ |
| Live preview of the running branch | – | Dev server per ticket |
| Content version-controlled in Git | ✓ | – |
| Code in your Git | ✓ | ✓ |
| Choice of Git host | GitHub, GitLab, self-hosted | GitHub only |
| Open source | ✓ | – |
| Self-hostable runtime | ✓ | – |
Choose Fredrin when you already hold a GitHub repository and a Claude or Codex subscription and the bottleneck is throughput of code changes, not getting a site to exist at all. Its agent mechanics are excellent and, in several places, ahead of ours: a real worktree and a running dev server per ticket so a reviewer sees the app and not only the diff, runtime, model and reasoning effort chosen per card, Goals that infer dependency order and run every unblocked ticket in parallel, a pre-push merge that refuses and names conflicting paths before a PR exists, a dispatch-time guard against tickets that contradict a settled decision, memory health flags with a one-click cleanup pull request, and desktop installers shipping on macOS, Windows and Linux while ours is not yet published as a download. Its flat workspace price on a subscription you already pay for is a real saving if you run many agents at once. If what you want is a board that ships code against a repo you own, it is the better buy — and it is candid that this is exactly what it is.
Visit Fredrin ↗Give Ever Works an idea and its agents research the space, write the content, generate the code, deploy it, and keep it improving — all version-controlled in your own Git.