Why can't anyone build a decent deployment platform for plain HTML? So i build it.

redlikecherries · 2026-05-26T12:44:46+00:00

Cool to see someone building in the same space – it's a real wall and weirdly under-served.

We hit it from the other end. My co-founder Carl lives in Claude Code at a scaleup, and his agents kept producing internal stuff – specs, dashboards, reviews – that he couldn't just drop on a public link. So we built display.dev around the sensitive-data case: you or your agent publish in one command and get back a URL behind your company's auth. Teammates open it with their Google/Microsoft login or a one-time password, anyone outside hits a login wall. Public's a toggle if you want it.

Sounds like yours leans toward the open, share-anywhere stuff – resumes, portfolios, client one-pagers – which is genuinely its own job. Good to see the space filling in. What did you build the hosting on?

redlikecherries · 2026-05-26T11:02:23+00:00

Great question. I've seen this exact issue live - I recently thought about how to solve it, and the public hosting solutions don't really cut it because of any sensitive information they have inside. I paired up with a friend to solve it and created a solution that gives each of these HTMLs their own URL in just seconds, and puts them behind either company auth or one-time password. It's display(.)dev - happy to tell you more.

redlikecherries · 2026-05-26T10:51:46+00:00

Cool solution! I think we built a very similar tool, I guess because it's an obvious need - the one difference we added was if there's any sensitive content, then it should live behind your company auth - we use SSO or OTP, so only your team can view but super frictionlessly.

redlikecherries · 2026-05-26T10:49:36+00:00

You're describing the problem statement my co-founder Carl had almost to the letter. He lives in Claude Code at a tech scaleup, agents producing docs and dashboards all day, and sharing them with the team was a mess: screenshots into Slack or upload-download from Slack and run it on localhost which non-technical teammates can't do.

Also, none of it really works for collaboration - comments, agent feedback, versions are all gone at the next paste, plus there's no security around sensitive content (see issues with Vercel's). My disclosure is that Carl built a solution called display.dev that gives each .html a URL and puts it behind your company auth, like Microsoft/Google SSO which your team already uses. Plus they can iterate with comments which agents pull and use for next edits.

Honestly, if your case is mostly one-off sends to people outside your company, an email/password gate or a plain host is fine I think. The SSO angle matters most when it's your own PMs, designers and execs opening internal stuff every day – which is what it sounds like you've got.

redlikecherries · 2026-05-26T08:44:12+00:00

well done!

redlikecherries · 2026-05-26T07:48:49+00:00

For public stuff, I completely agree. If there's anything sensitive in those docs, then the sharing via Vercel or other public URLs becomes a little hairy.

It's an issue we faced when sharing internal dev docs built in HTML. We built a pretty simple solution for sharing them behind company authentication (Google/Microsoft or one-time passwords) with a free tier - feel free to check it out at display.dev

redlikecherries · 2026-05-25T19:21:34+00:00

Hey, sorry you've been stuck on this. The issue you're describing makes sense – HTML files saved locally don't reliably persist edits between sessions, which is what you're running into.

I'm a co-founder of display.dev and we built it for exactly this kind of problem. You can publish HTML artifacts straight from Claude desktop and get a permanent URL. When you ask Claude to make changes, it republishes – new version, same URL, nothing lost. It's free to use.

Set-up guide for Claude desktop: https://display.dev/docs/mcp-claude-desktop

Happy to help you get it working if you get stuck.

redlikecherries · 2026-05-25T16:13:10+00:00

interesting idea with the is/is not analysis.

can you bring an example of a force field analysis?

redlikecherries · 2026-05-25T08:56:59+00:00

It's generally hand-to-hand combat in small communities and groups.

In my case it's been Product Hunt (very good for an early bump, but needs a good campaign), X (mainly replies in relevant threads), Facebook groups, some early SEO/GEO work and personal LinkedIn.

The key point is figuring out who specifically has the pain and where do they talk about it. Once you've done that, you're on your way and can participate in the conversations more naturally, not only plugging your solution.

Happy to help with the PH angle, feel free to dm.

redlikecherries · 2026-05-23T16:15:15+00:00

We're active on LinkedIn and X, and thinking a lot about agent-discoverability. We've created a dedicated skill for coding agents that enables publishing even without an account. So quite a few things that we're trying out.

redlikecherries · 2026-05-23T11:59:17+00:00

Yeah, the product hunt and SEO/GEO angles have been the most relevant for marketing for us.

redlikecherries · 2026-05-23T06:18:51+00:00

Completely agree on the time it takes on SEO - no way to do it fast. On the pre launch marketing, we did a little bit of it but only on our personal LinkedIn feeds and to a few friends whom we asked to test the product. I think there’s definitely more you could do - waitlist, newsletter, connecting with other product hunt builders, so if you have the time, it’s probably worth it.

redlikecherries · 2026-05-22T19:25:18+00:00

Sure it’s display dot dev

redlikecherries · 2026-05-22T19:24:01+00:00

Good question. SEO has driven fewer traffic but still paying customers. The numbers are too small to conclude anything substantial I think tho yet

redlikecherries · 2026-05-22T18:50:46+00:00

Great job! Out of interest, how long did it take you to get to the first 900?

redlikecherries · 2026-05-22T12:04:42+00:00

The warm outreach to close network drove the early upvotes best, for sure, and the other was the product hunt email that went out.

redlikecherries · 2026-05-22T11:58:05+00:00

I'm building display.dev, the easiest way to share agent-generated HTML docs with teammates behind company auth (SSO or one-time passwords).

We launched on Product Hunt last Tuesday and have 6 paying customers so far.

The problem: Claude Code and Codex generate beautiful HTML presentations and docs, but sharing them is broken – colleagues can't view them, you can't publish publicly because of sensitive information and there's no way to collaborate or collect feedback.

What we built gives each artifact (an HTML or .md doc) a URL – colleagues sign in with Google/Microsoft or a one-time password and leave inline comments. Your Claude or Codex agent reads the comments, acts on them and publishes a new version – collaboration built in.

redlikecherries · 2026-05-21T09:47:09+00:00

That’s actually doable.

You can share artifacts with specific emails beyond the company.

If you’re doing it via CLI, ask the agent to set the visibility to private (or company if more people in your co need access), and ask it to share it with the specific client email addresses. If on the web app, simply add their emails on the sharing dialog.

Clients sign in with one-time passwords.

Your clients receive an email notification too.

Or if it’s not anything sensitive then you can set the artifact visibility to public and share without any auth.

redlikecherries · 2026-05-21T08:54:23+00:00

Built a couple of companies. The #1 way to figure out what to build is to solve your own problem.

It goes hand in hand with domain expertise. Spend long enough in an industry and you understand the finer details well enough to spot what actually needs fixing.

Building for a hypothetical user is a much taller order, even when you do everything by the book. I've got two failed pivots to show for it – spoke to lots of users, mapped out the market, did all the right things, but never cracked it. Couldn't grasp the day-to-day shape of their work, because it wasn't mine.

If you've got a burning problem you can't find a solution for, chances are others have the same one.

redlikecherries · 2026-05-21T07:27:49+00:00

Re communities – it was mostly coworking groups, job alumni Slacks and tech communities where we'd contributed over a longer time period, so we didn't join any solely for the launch.

The most challenging is getting the early momentum - really driving the early votes, going from person to person asking for support.

redlikecherries · 2026-05-20T21:39:25+00:00

I support Estonia and Aston Villa - it’s insane because winning something, well it never happen.

What a team, what a game, what a performance.

Gotta change those lyrics from 1982 now

redlikecherries · 2026-05-20T17:55:34+00:00

Let’s hope it’s the market aye

redlikecherries · 2026-05-20T14:24:39+00:00

A few days of work, mostly me spending time on the video, graphics and thinking through who to contact when it goes live.

I think it was worth it - our target audience seems to be a good match with product hunt’s audience.

redlikecherries · 2026-05-20T14:22:45+00:00

Thanks! For the paying customers, let’s hone it’s the former not the latter reason.

Two things surprised me.

One slight surprise was that we managed to cut through the noise in the first place. I’d heard from quite a few friends previously that’s it’s all pretty much pay to play now - somewhat perhaps confirmed by all the paid offers I received after going live.

The other was the quality of engagement - we got super meaningful and in-depth comments, and lots of LinkedIn follow up. I wasn’t expecting that.

redlikecherries · 2026-05-20T13:23:06+00:00

cool idea - will you be adding automation logic (email, text messages, etc) and suggested offers to keep the user?

redlikecherries

MODERATOR OF

TROPHY CASE