What This Covers
Use this page to understand how seats are meant to feel in practice: what you buy, how seat use maps to your own systems, and what changes when activation must be completed offline.
Buyer FAQ
Straight answers for plugin buying decisions, seat handling, and the current offline activation workflow.
What To Do Next
If you still need a product-specific answer after reading, use the contact page before purchasing so we can confirm expectations for your workflow.
Contact UsBuying Decisions How do I know whether a plugin fits my workflow before I buy?
Start with the product page and focus on the practical scope: supported formats, supported platforms, whether the product is available now or still marked as coming soon, and whether the feature set solves a problem you already hit repeatedly.
If the decision depends on a specific DAW, operating system, or studio-machine setup, ask before buying. The goal is a clear fit, not a vague maybe.
Seats What does a seat mean from my perspective?
A seat is one activation slot for one machine at a time. In normal use, think of it as the right to keep the product active on one specific workstation or laptop.
If your purchase includes multiple seats, that usually means you can keep the product activated on the same number of your own systems without repeatedly moving the license back and forth.
Seats Can I use my seats across studio and mobile machines?
That is the intended use case for multiple seats. Many customers need one seat for a main production system and another for a travel or backup machine.
The key expectation is still personal use within the purchased seat count. If your setup is unusual, ask first so the purchase matches the way you actually work.
Offline Seats How does an offline seat work from the user side?
An offline seat is meant for a machine that cannot reach the internet during normal use. Instead of live activation on that machine, you use a two-machine exchange with request and license files.
Typical flow: generate a .awx-request file on the offline machine, upload it from an online machine in your account License Manager, download the resulting .awx-license file, then bring that file back to the offline machine and apply it.
Offline Seats Do offline request files expire if I wait too long to upload?
Yes. Offline request files are time-windowed, so waiting too long can make a request invalid. If the upload is rejected as expired, generate a fresh .awx-request on the offline machine and upload that new one.
This window exists to reduce replay risk and keep offline issuance tied to current machine state.
Offline Seats Do offline seats behave differently after activation?
Offline licenses are valid for a defined key period and include a hard expiry date. When the key expires, generate a new offline request and repeat the exchange to renew activation.
If a hardware change, OS reinstall, or major workstation rebuild affects machine identity, you should also expect to run the activation flow again so the seat aligns to the updated system.
Offline Seats Why did my offline request go pending instead of downloading instantly?
Most requests are auto-fulfilled when checks pass, but some can be queued for manual review. In that case your request stays pending until fulfilled, then the license file becomes available for download in License Manager.
If you are blocked by timing, contact support with your product, account email, and the offline machine context so we can help quickly.
Support What should I ask before I buy if I am unsure?
The fastest useful questions are concrete ones: your operating system, your DAW, whether the target machine is online or offline, and how many of your own systems need active access at the same time.
That gives enough context to answer honestly and helps prevent a purchase that fits on paper but not in your real setup.