Let your team change your custom site without touching code
Ask for a new landing page, a pricing plan or a signup form, and Daytwo builds it on your Next.js or Astro site from your own brand and components. It waits in a private draft until someone on your team approves it. Publishing is a normal commit to your GitHub repo, your developers keep working as usual, and it runs on your own Claude plan. Stop using Daytwo and your site keeps running exactly as it is.
Hi Product Hunt! Simon here, I'm building Daytwo with @robinwaroquier
At ++addmore, a product marketing and brand studio, we build websites for the startups we work with. This year we moved our client sites from Webflow and Framer to Next.js and Astro. Better sites, but the marketing teams running them don't know GitHub, Vercel or coding agents, and they shouldn't have to. So every new landing page became a Slack message to us developers, or more often it never shipped.
Daytwo gives that team their site back. They ask for a new page, a pricing section or a signup form, in the Mac app or by tagging Daytwo in Slack. It's built from the site's own brand and components in a private draft, and nothing goes live until someone on their team approves it. Approvers don't even need the app: they review in Slack, by email or in any browser.
For the engineers, nothing changes:
A draft is a branch, publishing is one commit, undo is a revert
You keep pushing to the repo like you always did
It runs on the team's own Claude plan, the app sets up Claude Code for them
Stop using Daytwo and the site keeps running exactly as it is
It's Mac only, and it works with Next.js or Astro sites on GitHub and Vercel (Astro on Cloudflare works too). A developer connects the repo once.
There's a free 14-day trial. We'd love to hear what your team would build first, and what's missing for your setup.
About Daytwo on Product Hunt
“Let your team change your custom site without touching code”
Daytwo launched on Product Hunt on November 10th, 2026 and earned 70 upvotes and 6 comments, placing #27 on the daily leaderboard. Ask for a new landing page, a pricing plan or a signup form, and Daytwo builds it on your Next.js or Astro site from your own brand and components. It waits in a private draft until someone on your team approves it. Publishing is a normal commit to your GitHub repo, your developers keep working as usual, and it runs on your own Claude plan. Stop using Daytwo and your site keeps running exactly as it is.
On the analytics side, Daytwo competes within Website Builder, Artificial Intelligence and Development — topics that collectively have 500.2k followers on Product Hunt. The dashboard above tracks how Daytwo performed against the three products that launched closest to it on the same day.
Who hunted Daytwo?
Daytwo was hunted by Simon Demeulemeester. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Daytwo including community comment highlights and product details, visit the product overview.
Hi Product Hunt! Simon here, I'm building Daytwo with @robinwaroquier
At ++addmore, a product marketing and brand studio, we build websites for the startups we work with. This year we moved our client sites from Webflow and Framer to Next.js and Astro. Better sites, but the marketing teams running them don't know GitHub, Vercel or coding agents, and they shouldn't have to. So every new landing page became a Slack message to us developers, or more often it never shipped.
Daytwo gives that team their site back. They ask for a new page, a pricing section or a signup form, in the Mac app or by tagging Daytwo in Slack. It's built from the site's own brand and components in a private draft, and nothing goes live until someone on their team approves it. Approvers don't even need the app: they review in Slack, by email or in any browser.
For the engineers, nothing changes:
A draft is a branch, publishing is one commit, undo is a revert
You keep pushing to the repo like you always did
It runs on the team's own Claude plan, the app sets up Claude Code for them
Stop using Daytwo and the site keeps running exactly as it is
It's Mac only, and it works with Next.js or Astro sites on GitHub and Vercel (Astro on Cloudflare works too). A developer connects the repo once.
There's a free 14-day trial. We'd love to hear what your team would build first, and what's missing for your setup.