I built a complete cloud IDE that runs entirely in your browser. Here's why I think it matters.
My name is Augustine. I'm a developer and I've spent the last several months building Cloudpen, a professional cloud development environment that works in any browser on any device, including your phone.
I want to share what it is, why I built it, and what makes it different from the other browser IDEs you've probably already tried.
The problem I was solving
The developer tooling stack has become expensive and fragmented. If you're using VS Code, GitHub Pro, Vercel, and GitHub Copilot, you're paying $50 to $80 a month across four separate tools with four separate logins. For developers in emerging markets, that's not a small number. And none of those tools work well on a phone, which for a lot of developers globally is their primary device.
What Cloudpen actually is
Cloudpen brings everything into one browser tab. You get a professional code editor (the same engine behind VS Code), a real PTY terminal over WebSocket, one-click deployment to a live URL with automatic SSL, a built-in AI assistant called Quill, GitHub sync with webhook auto-redeploy, and real-time team collaboration with role-based permissions.
Everything. One tab. $12 a month. No installation.
What makes it genuinely different
Three things that I haven't seen any other cloud IDE do together:
First, it works fully on a smartphone. Not a stripped-down mobile view. The actual editor, terminal, file tree, search, and deployment all work on your phone. I built this deliberately because a lot of the developers I care most about are mobile-first.
Second, one-click deployment is a first-class feature, not an afterthought. You write code and you get a live URL with SSL in seconds. No separate Vercel account. No config files. Just click Deploy.
Third, the price. At $12 a month Pro replaces tools that together cost $50 to $80. For students it's $6 a month, every renewal, not just the first month.
Where it is today
Cloudpen is live at cloudpen.dev. We have active users, the platform has been tested by developers locally and internationally, and it's working. I'm building in public and I'm genuinely interested in feedback from other developers.
If you've been frustrated by how expensive and fragmented the standard dev setup has become, I'd love for you to try it.
cloudpen.dev — free to start, no card required.
Augustine
Posted on
Cloudpen Launch
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
Congrats on the launch - shipping anything publicly is the hard part most people never clear, so that's worth celebrating regardless of what happens next. One unsolicited launch-day note from doing a few: the launch is a spike, not a strategy - the traffic fades in 48h, so the highest-ROI move right now is capturing the people who showed up (email, a clear next step) rather than refreshing the upvote count. The post-launch follow-up converts far more than launch day itself.
Genuinely curious what Cloudpen does - the post is light on the "what + for whom," and that one-liner is what determines whether a launch-day visitor sticks. (Tangent from someone who launched recently: leading with the concrete outcome + a zero-friction trial moved my numbers most - for Moonshift it's "prompt to a shipped SaaS on your own GitHub + Vercel, first run free, no card.") What's Cloudpen's one-sentence pitch and who's the first user you're chasing? Happy to give launch feedback if useful.
Appreciate this more than a generic "congrats." It's genuinely useful framing.
You're right that the launch spike is not the strategy. I've already been thinking more about what happens after the launch than the upvote count itself, specifically how to capture the people who show up and give them a clear next step instead of sending them to a generic homepage.
On the one-liner, that's fair feedback. The post was written to explain the problem and the build, but you're pointing to something more important: the concrete outcome for the first person I'm trying to convert.
The honest answer is that the first user I'm targeting is a developer who wants to deploy and share a project but keeps running into friction before getting there. The one-sentence pitch that has been resonating is: "Write code, click deploy, and share a live URL in seconds. No Vercel account required."
The zero-friction trial is the free plan. Users get real code execution, terminal access, and deployments without needing a credit card.
The "who" is harder to compress into a single sentence without excluding people, but if I had to choose, it would be developers who finish projects more often than they ship them.
I'd genuinely value your feedback on whether that framing lands or if it still feels too broad.