Start with included credits, add advanced control later
Most people should start with included credits. Studios that need direct billing can connect their own provider account on Studio.
New users who want no setup, plus teams that need provider control later.
DriftLess starts simple with included credits, then exposes advanced account control only when it is actually useful.
Asking new users for keys before they see value creates friction. Hiding advanced control forever frustrates technical teams.
From idea to reviewable version
The steps below keep the work practical for business owners while leaving technical handoff available when it is needed.
Version flow
- 1Use included credits to create the first version.
- 2Top up with packs if you need more hosted usage.
- 3Move to Studio if your organization needs its own provider account.
- 4Keep the same workflow while changing the billing path.
Review checks
- Setup check: can the user start without technical configuration?
- Usage check: are the included credits understandable enough to continue?
- Control check: does the team need direct provider billing now or later?
Why this matters
Each path gives visitors a concrete reason to try DriftLess without making them learn technical language first.
First Look and Maker start without any advanced account setup.
Studio can connect advanced keys for direct billing.
Usage tracking keeps credits understandable.
The simple path and technical path can coexist.
Do I need a provider account to start?
No. First Look and Maker use included hosted credits. Studio unlocks advanced keys when direct billing and specific model control matter.
Why keep the advanced option?
Some teams need direct provider billing, approved models, or their own account controls. That should be available without becoming the default first step.