Use the interest path for founder follow-up and workload planning. Use the feedback path for bugs, onboarding friction, or support. Both routes land in the real product review flow.
Capture your team, use case, expected volume, and what you care about most so follow-up can stay relevant for the current devnet alpha.
Use this for launch planning
The clearest founder follow-up starts with concrete workload detail and a clear next question.
The workload you want to validate on devnet and why now is the right timing.
Your expected request volume and whether standard RPC or priority relay matters.
Whether analytics visibility, managed rollout help, or operator participation matters to your team.
Use the channels that fit the conversation best.
Two distinct queues
Use this when you hit something confusing during wallet auth, project activation, funding, key creation, or your first relay request.
The best support reports are easy to replay and easy to route to the right part of the stack.
Call out the exact page or step where the friction started.
Include whether the issue is blocking first request setup, funding confirmation, or API key usage.
Say whether the project is already activated and funded so support can separate onboarding friction from funded relay behavior.
Use the interest form above instead when the main question is fit, rollout planning, pricing context, or a founder review of the workload.
Private alpha support posture
