No API keys. No private prompts. We only need enough context to shape the first beta.
This helps us decide whether the first MVP should be developer-local, Docker-first, team-facing, or cloud-hosted.
Choose everything that is part of your current workflow.
The pool can mix local workers, frontier APIs, open models, and internal services.
Choose up to three. This decides the first routing and eval policies.
We are using this answer to decide the first deployable shape.
We use this to plan beta access, user interviews, and contributor collaboration.
These optional fields help us design the eval harness and contact the right beta users.
Do not paste secrets, API keys, customer data, or private prompts. The waitlist only collects product-prioritization signals.