ADDOM is being shaped with a small number of serious users first. This path is for teams and developers who want early access, direct contact, and a tighter feedback loop around real repository work.
Private alpha
Direct collaboration, small surface area.
ADDOM is being shaped with a small number of serious users first. The current path is private alpha and design-partner collaboration, not a broad public rollout.
Who this is for
The alpha is for technical users with real workflows.
Good fit
Solo developers
real codebases
Small product teams
feedback-rich workflows
Agencies
controlled client work
Privacy-sensitive builders
local-first preference
Not the target
This is not aimed at casual chat users, teams expecting a polished mass-market product immediately, or anyone looking for a fully hands-off autonomous coding system.
The point is serious workflow fit, not broad consumer reach.
Design partner
Direct collaboration for teams with real workflows.
Private builds, direct builder communication, early access to new capabilities, and meaningful input into the workflows that matter most to you.
Real usage, clear feedback, reproducible issues, workflow pain points, and honest reporting from actual codebase use.
Collaboration structure is discussed directly once workflow fit is clear.
Process
How the alpha path works.
Start with the form
Describe your stack, team size, and where current AI tooling breaks down for you.
Check workflow fit
If the use case aligns, move into a short conversation or direct async follow-up.
Get a private build
Use ADDOM on real work, not synthetic demos.
Iterate tightly
Report friction, bugs, and workflow gaps so the product can improve in the right direction.
Start with a conversation
If your current AI coding setup feels too opaque or too shallow, this is the right stage to talk.
Private alpha exists so the product can be improved with high-signal users before broad exposure.