Appreciate you trying it and commenting. And I'm sorry that you hit this bug on first contact. My goal is to have a dead-simple UX, not waste your time trying to get it working. Heck, the whole point of Rocky Surf is convenience.
I've filed this as a bug.
Per your comment about the documentation - I agree that the docs aren't great for humans. In fact, they're meant to be read by agents, not humans. But I don't make this clear anywhere.
During this build, my development agents were instructed to be verbose with documentation. I find that this improves code quality and architectural consistency across multiple agent sessions - Rocky Surf was built over hundreds of agent sessions. The trade-off is that there's too much for humans to read.
As I got closer to release, I read, edited, and pruned a considerable amount of verbiage, but stopped short of making concise docs a release requirement. But the fact that you noticed that a particular doc was 40 pages tells me that I didn't value your time as much as I should have. Duly noted.
Its been used by a lot of fringe types since the 1960s, and was at one time popular among Rastafarians. It's also a little used sailing term. Here it functions merely as satire.
Enterprises need a solution like Lovable or Replit if only for the one-touch deployments. Unfortunately, neither tool is there.
I don't know what's taking Anthropic, OpenAI, Google, Microsoft, even AWS to build deployments themselves. There are only a handful of reference architectures for vibe-coded apps.
There is too much friction in deploying internal tools. I have been building https://github.com/openrundev/openrun to solve that. Full GitOps (create/update your app through GitOps, not just updating app source code), staged deployments, service bindings (for getting a managed database credential, instead of creating a new database per app) and OIDC/SAML with RBAC.
Very interesting project! I haven't fully read through yet - does it deploy to existing resources/infra, or does it handle resource/compute provisioning as well? How are you handling keys/creds?
Do you have any real users yet?
I'm working on a open resource/compute provisioning protocol/system (not released yet), targeting both cloud platforms as well as internal, which may go hand-in-hand with what you're building.
OpenRun runs on a single machine, with either Docker or Podman. All apps runs on that one machine. Idle apps are scaled down to zero, so resource usage is low even when hundreds of apps are installed. For scaling up, OpenRun can be deployed on Kubernetes. Each app deployed through OpenRun gets created as a Kubernetes deployment, again with scaling down to zero. Same declarative config moves from singe node to Kubernetes, no changes required.
I don't have any telemetry, so not sure about number of users. Based on issues filed, lots of users using the single node deployment (which is good enough for most use cases). Started with Streamlit/Gradio type apps, now users are actually using it for deploying vibe coded internal tools. See https://github.com/openrundev/openrun/issues?q=is%3Aissue%20...
IMO you should evolve also as a central platform to host AND build internal tools (eg with agents). Have you considered that? EDIT oh snap I see in the console tour that there's an AI App Builder section. Ok gonna have to try this out then!
Also does your git integration support self-hosted Bitbucket (I guess at the least generic git instance not just GitHub etc) ?
Also, pretty cool that you have a FastHTML spec.. I built this (well AI mostly did) with FastHTML: https://hn-readtheroom.exe.xyz/
The agent based app builder is pretty new, still improving it. It runs with Agent Client Protocol (ACP), with integrations for Claude Code, Codex CLI, OpenCode and Pi.
Thanks! That's sounds excellent. I love the Shelley Web Agent ( https://GitHub.com/boldsoftware/Shelley ), but guessing it would be hard to integrate that into your platform (although would be amazing if you could).
OpenAI has a feature they rolled out several weeks ago called Sites that takes care of deployment with one click (hosting, database, auth). It’s so much easier for non-technical now to vibe code and publish their app
I use AI explainers a lot in my own projects and have skills that give outputs I like. I'll even pipe the output into NotebookLM to make a video sometimes. This is actually a decent way to grok complex subsystems (YMMV).
What I don't care for is the pretty-yet-verbose HTML outputs that I see from some teams. They can be way too long and it's often the case that the engineer who made it didn't read the whole thing.
reply