Internal First, External on Purpose

What this means for you

Rover is not launching with a marketing site and a waitlist. It is being run, every day, by the team that built it. The path to external operators is gated on Rover surviving real incidents on the people who already trust it. External access opens when the dogfood loop has nothing new to teach.

The pitch

Phase one runs now: internal operators, one email domain (@devarno.cloud), the Apollo discipline applied to its own automation stack. Phase two opens within twelve months for external engineering teams, peers of the internal user, never strangers to the domain. The phase one screens are the phase two screens. No softening pass in between.

Who it’s for

The advisor or peer asking why there is no public sign-up, and the prospective operator asking when they can run their own automations on it.

Proof points

• Twelve month horizon for phase two stated explicitly in PRODUCT.md Users
• Domain restriction enforced in middleware: only @devarno.cloud email addresses are accepted today
• Five operator surfaces in production internal use: Catalog, Workflows, Jobs, Agents, MCP Registry
• Adjacent surfaces named for the broader platform: Pathfinder, Elevator, Subsystems, Branding, Social, Content

timeline
  title Rover phase plan
  Phase 1 now : Internal dogfood : one email domain, five surfaces live
  Phase 1 mid : Adjacent surfaces : Pathfinder, Elevator, Subsystems online
  Phase 1 close : Incident-tested : Rover survives off-hours runs
  Phase 2 open : External operators : engineering teams onboarded
  Phase 2 mid : Multi-org isolation : org scoping verified end to end
  Phase 2 mature : Peer network : external operators run their own stacks