Public: anyone can read this; the crew can change it.

One click from a stranger to their own forge: sign up, make a forge, it is live - on the vxrail, decoupled from open-platform #2914

shipped production is serving it opened this has it
opened this

Owner (trevato), 2026-10-19: "the new forge workflow needs to be rock solid. i want grokbot to be able to make its own completely autonomously. eventually our company will sell forges but i want one click deploy ... from anon. of course they should be required to make an account but decouple from open platform. user name and password is fine. email could be optional ... the vxrail has a ton of resources ... I want to have a ton of forges. i wanna send to my friends and they just get it. 'oh ill just make an account then make my forge' then they should be able to include any of my public apps too like cs-engine ... i could have a serious forge with dedicated resources and a fun forge with dedicated resources."

Done (plan it as small issues; this is the program):

  1. Account: a stranger signs up on this forge with username + password (email optional, never required today); no open-platform / Forgejo / edge account involved anywhere in the path.
  2. One click: signed in, "Make my forge" asks only a name and a size, and the forge is live at its own address within a stated budget (target: under 3 minutes), with the new owner as its first admin (the operator's first-admin path, no code to copy).
  3. Resources: each forge runs with dedicated, declared resources on the vxrail (size presets, e.g. small/medium/large: CPU, memory, disk; quota enforced), and the owner of many forges sees them side by side ("serious" and "fun" forges).
  4. Apps: at creation the new owner can pick any public app from the parent (e.g. cs-engine) to include, and it deploys in the new forge.
  5. Agents: grokbot or any agent with a token can do 1-4 end to end through the API/MCP alone, unattended.
  6. Rock solid: an end-to-end test (and a nightly drill on the vxrail) goes anonymous -> account -> forge live -> app included -> health answers, and fails loudly with the step that broke; /boards shows forges made, time to live, and failures.

Related: #1454 (New forge door), #1384 (child apps), #2410/#2243 (cell resources).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs