Quota Video Sampler
Current testing wave Beta Stable Experimental Nightly

JOIN THE CURRENT WAVE.HELP SHAPE MINI.

Mini Beta is open during the current testing wave. This page only captures your email and unlocks the Discord handoff. Quota Bot handles the real onboarding after you join — platform, workflow, tools, and the rest.

Active testers who provide meaningful feedback may be invited to continue beyond the initial trial period.

How it works
  1. 1. Enter your email on this page
  2. 2. Land on the beta welcome page
  3. 3. Join Discord and complete the short onboarding about your platform, OS, workflow, and tools
  4. 4. Grab the latest recommended build there and start testing
Access policy

Start with the trial. Continue by contributing.

Beta access begins with the standard 30-day Mini trial. During the current testing wave, testers who actively participate and provide meaningful feedback may be invited to continue beyond the initial trial period.

  • • Join the beta Discord and use the recommended beta build
  • • Report bugs clearly and include useful reproduction details when possible
  • • Share workflow feedback based on real sessions, not just first impressions
  • • Continued access is reviewed case by case to keep the beta focused, useful, and high-signal
Beta signup

Get on the beta list

Use the same email you would use for the Mini trial or a future purchase so the audience stays clean. Once you submit, you’ll land on the beta welcome page with the Discord handoff, where Quota Bot will collect the rest of your onboarding details.

This page only captures your email for the Quota Mini beta list. Quota Bot handles the real onboarding after you join Discord — platform, OS, workflow, and tools. No long form here.

What happens after signup
  • • You get added to the Quota Mini beta list in Brevo
  • • You land on the beta welcome page with the Discord invite + next steps
  • • Discord onboarding will ask for your platform, OS, workflow, and software / hardware stack — DAWs, NLEs, samplers, grooveboxes, controllers, etc.
  • • Once approved, the beta channels unlock inside the server

Most testers should stick with Beta Stable. Nightlies are for people who are comfortable with rougher builds.

Beta Stable = recommended build for most testers Experimental Nightly = newer build, may break Continued access is reserved for active testers
Bug reports

What to include

  • • app name
  • • build version or build date
  • • OS
  • • hardware details if relevant
  • • steps to reproduce
  • • expected result
  • • actual result
  • • screenshot or logs if you have them
What counts as participation

The kind of feedback that matters

  • • Testing real sessions instead of only quick first impressions
  • • Clear bug reports with steps, screenshots, or logs when possible
  • • Workflow feedback tied to actual use cases
  • • Follow-up confirmation when a fix or new build is ready to test