Aleš @fxckdev_

I built a multiplayer Figma -style mood- board and never touched a server 👇 Claude Code ran inside @zeropsio ZCP (an AI control-plane that lives in your project) and spun up everything: ✓ Postgres ✓ Valkey ✓ object storage ✓ a websocket server ✓ the Vue frontend ✓ a PNG-export worker Then deployed & tested it live. Two windows, live cursors, instant sync. No local setup, no secrets. Try it: webstage-252e.prg1.zerops.app youtu.be/Bg6Bw2V9QAQ

I can confirm models can indeed do stuff. But imagine a platform where you use real IDE, Claude Code, your subscription. A place where the main point is not to generate something with as few prompts as possible, but to build and maintain scalable production systems. 🤔 @zeropsio

Benjamin Verbeek @benjaminvrbk

a day ago

Two prompts with Fable in @Lovable: 1/ "build a copy of Spore space-age part, where you can fly your spaceship between stars, zoom into planets and upgrade your ship etc." 2/ "Make it multiplayer."

15 9 170 24K 98

@massimodeluisa @expo @reactnative @X Yet X lets p*rn bots follow me :/

@tobi Do they get some secret sauce? Or what prevents me from creating Shopify frontends with anything (like Zerops)?

@Lindyydrope @grok evaluate

@Lindyydrope Oky hear me out.. docs.zerops.io/features/codin…

Definitely, marketing sites are where a lot of the focus is right now (Lovable, ChatGPT sites etc.), because that's where VCs imagine they can replace developers. But then there's everything else, things that use databases, storage, auth, search, CRUD endpoints, anything beyond a static site. And imo in the end, unless it's just a quick marketing prototype that will be trashed later, I think it's definitely worth following good development practices anyway, even if it's a non-developer working on the thing.

I believe it's all about maintainability. > Agents should handle the mechanical work of implementing, updating, and maintaining the system. Yes, but what if something breaks and a human developer needs to look or take over - when everything is either in a black box, or the agent was let loose on a VPS, you're pretty much screwed. I feel like the answer is a developer-first cloud platform that can handle the whole development lifecycle from local / remote development to production, and you then make the agent a power user of that. People are reinventing the wheel. I just think about coding agents like human developers, and want to give them the same thing that would empower a human developer.

@FrancescoCiull4 They don't know..

Imagine this, but instead of a blackbox the output would be a production ready, transparent infrastructure using standard OSS for databases, queues, storage, search services, CI/CD, remote development environment where you can jump in at any point and code that sits in your GitHub repo. 🤔 👉 @zeropsio

Rohan Varma @TheRohanVarma

a week ago

We just launched Sites into Codex! Software creation was always about more than writing code. Sites in Codex fundamentally gives the power of end-to-end software creation to every user, no matter their technical fluency. These Sites are fully deployed to a URL, private to

241 267 4K 1.0M 2K

Exactly right: "realistic development environments". But let me take it a step further, not only they need realistic dev environments, they need environment parity between that dev environment and production environment. That's why way to go, but you for that you have to start with cloud platform first, then add agent, not the other way around: docs.zerops.io/features/codin…. Looking forward to seeing how well it works with Cursor as well. Getting there.

keyboard_arrow_left Previous keyboard_arrow_right Next

🙂.. but also the Hermes dashboard, accessible privately through the WireGuard VPN built into our CLI.. and SQLite databses backed up with Litestream, which is running as a second process (because we use system containers) @zeropsio just a quick version (github.com/fxck/recipe-he…), but no worries, things are coming together.. an official Hermes recipes and much more coming soon

keyboard_arrow_left Previous keyboard_arrow_right Next

Railway @Railway

a week ago

Railway's built in SSH console 🤝 Hermes Agent by @NousResearch Video tutorial dropping soon

5 3 146 33K 37

@kunalpsingh25 @aahiknsv @zeropsio > One question , What is the use case? I'm pretty sure the use case was to build something quick and fun to get hands-on with the product of a company she just joined. Glad I could help figure this out!

Exactly! If you put the first two paragraphs into the chat, it would explain Zerops to you better as I, or any content on the website would, because it would be personalized to your case. 🙂 In practice Zerops could be many things to a wide range of use cases, each with need for a different explanation, each seeing benefits in different places. That's why I chose the chat as the primary CTA and targeted the rest of the page to the people where I think we'll have the highest chance to convert them. Sorry about the bug - unhandled unpublished job posting (already filled). I plan to do a larger set of updates to the website this month, integrating docs.zerops.io/features/codin… more deeply, will fix it along with it.

@FrancescoCiull4 you start with GIFTube, you end up with YT clone

@noa_dfx @FrancescoCiull4 zerops.io

@FrancescoCiull4 @zeropsio @domirosari0 I have so many more analogies in my bag. Have I ever told you the one about a coctail bar?

Hey @domirosari0, following up personally since I'm the one responsible for the overwhelming design 🫠 there's a method to the chaos, and it's an interesting problem to solve if you happen to want to indulge more. We're way too late to the PaaS game, 7 years building the platform (for reasons that'd make a decent Netflix comedy), so we're technically mature but only just showing up to a party where everyone already knows everyone. The PaaS market has a pretty fixed vocabulary, eg. managed Postgres, private networking, autoscaling, preview envs, one-click deploy. Every platform ticks the same boxes. Ask anyone "do you have Postgres?" and the answer is always "yes." But our entire reason to exist lives in the operational differences behind those same words. Our managed highly-available Postgres on a real private network isn't docker compose up on a Postgres image. SSHing into a full system container isn't SSHing into a microVM running docker. Same words, completely different thing.. and you mostly only feel it once the other version has burned you. Which is exactly the landing-page problem. You can't sell that nuance with keywords, because the mindshare for those keywords is already owned by Railway, Vercel, Render. We'd just sound like everyone else. Thanks to the architectural decisions and philosophy we built the platform around from the ground up, Zerops is affordable and usable for a wide range of use cases, from a $1/m Next.js static site, to infra for an agency juggling client projects, to a base layer for large distributed systems. That's also why chat is the main CTA. To explain how the operational nuances could help you, we need to understand your use case, where you're coming from. With that, we can reframe what you'd call "overwhelming" into digestible text personalized for what you need. Recipes (one-click examples below the fold) are the second-best path a visitor could choose, you get to try the actual product without having to lift a finger (except once, after you click confirm on which tech stack you want to demonstrate). If you don't take us up on these two "offers", the feature wall is the third, but it's for the experienced crowd, the ones that got burned by the "other version". The whole website self-selects on purpose, as a similar philosophy is ingrained in the platform itself. We're not optimizing for deploying the first app in 30 seconds with no configs, but for day 365 of your app running. And if your needs and wants are elsewhere, it's likely you'd be happier on Railway anyway. All that said, you're not wrong that some of it can and should be tightened, and a few sections are genuinely still unfinished, but I'm happy to say that significantly more effort over years of development was put into the platform, so an SVG not rendering properly in some edge cases definitely doesn't affect our ability to keep your apps running and your data safe. Appreciate you actually taking the time to look. Keep that eye on us. 🫡

So far 4.8 seems like a HUGE downgrade from 4.7, which seemed like a big downgrade from 4.6. What's going on?