← About Console
Contents

Ownership.
Simple & Flexible.

Devices
2 devices included
+1 per additional seat
Transfers
3 per rolling 180 days
+1 per additional seat
License
Annual license check-in
Automatic or manual

Routine license maintenance. Uninterrupted work.

Get licensed

01Activating your first deviceConnect your account, select your product, and authorize this device.02Adding a second deviceKeep a studio device and a laptop authorized under the same purchase.03Adding a seatRun the same product on one more device at the same time.04Authorizing an offline deviceAuthorize an offline studio device using Console on a connected device.

Stay licensed

05Working offlineRun an activated product without a live Console account or cloud session.06Automatic license renewalKeep your license current, even when Console is closed.07Renewing manuallyKeep control of renewal, with an online check or an offline file exchange.

Change devices

08Moving to a new deviceRelease an occupied seat, then authorize the replacement device.09Lost or broken deviceFree an unavailable device’s seat from another connected device, or from your account.10Restoring a missing licenseRecover the signed file for a device that still has an active server seat.

Get licensed · Start Here

Activating your first device

Connect your SWEG account, choose your product, and authorize this device.

  • 1 of 2 included seats
  • Native formats share a seat
  • 4 steps
All scenarios

  1. This Device

    Connect Console

    Open the Account menu and connect your SWEG account. Approve device management in the browser, then return to Console.

    You doConnect accountYou seeAccount connected

  2. Library

    Select your product

    Choose your native product and check the seat marked “This device.” Install the product if you have not already done so.

    You doYour productYou seeThis device

  3. Licensing

    Choose Authorize

    Choose Authorize for this device and wait for the confirmed result. This allocates a device seat and saves a verified, signed license.

    You doAuthorizeYou seeThis device is authorized

  4. Ready

    Check your renewal choice

    Review automatic renewal in Settings. Complete renewal consent if offered; check that its status is On, or deliberately leave it Off.

    You doAutomatic renewalYou seeReview On / Off

What you get

This device is licensed. Native formats of the product use the same license and device seat.

Keep in mind

Automatic renewal is offered during setup. Check that Settings shows On once you have approved it, or use manual renewal when you need it.

Get licensed · Another Device

Adding a second device

Use your remaining included seat on another device. You do not need to release the first seat when a second is available.

  • 2 seats included
  • Formats share a seat
  • 4 steps
All scenarios

  1. Second Device

    Open Console there

    On the second supported device, connect the account that owns the native product. Each device needs its own license.

    You doConnect accountYou seeOwning account

  2. Library

    Inspect the available seat

    Select the product and review the verified seats. “This device” identifies the device you are currently using.

    You doSeat availableYou seeThis device

  3. Licensing

    Authorize this device

    Choose Authorize and wait for confirmation. The second device receives its own signed license bound to its identity.

    You doAuthorizeYou seeSecond seat active

  4. Ready

    Use any native format

    Native formats of the product, such as AU and VST3, share this device’s seat. Switching between them on the same device does not require another activation.

    You doAU + VST3You seeOne device seat

What you get

Both devices have their own licenses, within the included two-seat capacity.

Keep in mind

Two included seats means two authorized devices per product purchase. Need a third? Add a seat to that product. Seats do not establish a multi-user, rental, or resale right.

Get licensed · More Devices

Adding a seat

Every product purchase includes two seats. An additional seat adds one more simultaneous device to that product’s licence, and one more transfer to its allowance.

  • +1 device
  • +1 transfer
  • 4 steps
All scenarios

  1. Library

    Check the seat tiles

    Select the product in Console. Each seat has its own tile; this device is shown first, and a lighter border marks its active seat. Seat numbers stay stable when tiles move.

    You doLicence tilesYou seeAll seats occupied

  2. Console

    Choose +

    Use the + control beside the tiles. It opens the additional-seat area of your SWEG account for that product.

    You do+You seeAccount opens

  3. Account

    Buy an additional seat

    Complete checkout for one additional seat. It attaches to that product’s licence only; seats do not move between products.

    You doAdd a seatYou seeSeat added

  4. New Device

    Authorize as usual

    Back in Console, choose Authorize on the new device, or use Remote Auth if it is offline. The new seat behaves exactly like an included one.

    You doAuthorizeYou seeDevice licensed

What you get

That product can now run on one more device at the same time.

Keep in mind

An additional seat is its own order with its own 14-day refund window. Returning it reduces capacity: you choose which devices are affected, and renewal stays available while a request is pending. Included, purchased and support-granted seats activate and renew identically.

Get licensed · File Round Trip

Authorizing an offline device

The studio device can stay disconnected. A request file identifies it; the connected device obtains a signed license for that target.

  • Offline target stays offline
  • Target uses the seat
  • 5 steps
All scenarios
Offline target Studio device Saves the request and imports the license.
Connected device Any device running Console Signed in to the owning account. Needs no seat of its own to export.

  1. Offline Target

    Save a request

    Open the target device’s Licensing / Import panel. Give it a recognizable label and choose Save request to create its .swegrequest file.

    You doSave requestYou see.swegrequest

  2. File Transfer

    Take the request online

    Copy that request to a connected device using removable storage or another suitable file-transfer method. Do not substitute the connected device’s request.

    You doTarget requestYou seeConnected device

  3. Connected Device

    Authorize + export

    Connect Console to the owning account. Choose Remote Auth, then Load request. Review the target, choose Authorize + export, and save the returned .json license.

    You doAuthorize + exportYou seeSigned .json license

  4. File Transfer

    Bring the license back

    Return the exported license file to the original offline device. The request file and the signed license are different files.

    You doSigned licenseYou seeOffline target

  5. Offline Target

    Import and verify

    Choose Import licence and select the returned .json file. Wait for successful local verification before relying on the authorization.

    You doImport licenceYou seeLicense verified

What you get

The target device is licensed without needing its own internet connection.

Keep in mind

Saving a request does not reserve a seat. Authorize + export allocates the target’s seat, or retrieves its existing seat. The helper device does not need its own activation merely to export. Remote Auth is a file exchange, not a remote desktop connection.

Stay licensed · In The Studio

Working offline

Once your device is authorized, you can work without a continuous internet connection.

  • No continuous connection
  • Manual renewal available
  • 3 steps
All scenarios

  1. Before You Go Offline

    Check your license

    Open Licensing / Import and confirm that your product is licensed. Review the license status before a long offline period.

    You doLocal licenseYou seeLicensed

  2. In Your Daw

    Work as usual

    Open your project and use the product. You do not need to keep Console open or stay signed in to your account.

    You doOpen your projectYou seeReady to work

  3. When A Check-In Is Due

    Refresh the license

    Renew online when convenient, or use Remote Auth to bring an updated license file back to this device.

    You doRenew online or by fileYou seeLicense updated

What you get

Your authorized device is ready for offline work.

Keep in mind

For an offline studio, follow “Authorizing an offline device” to bring back an updated file. Renewal reminders do not interrupt a perpetual product’s audio.

Stay licensed · Set And Check

Automatic license renewal

Turn on automatic renewal once. Console can then keep this device’s license current in the background.

  • Runs in the background
  • Same seat retained
  • 4 steps
All scenarios

  1. Settings

    Turn automatic renewal on

    Use “Automatically renew licences on this device, even when Console is closed.” An eligible, verified native perpetual license must already exist.

    You doAutomatic renewalYou seeEnable

  2. Browser

    Approve renewal permission

    Complete the browser consent when requested. Console saves renewal permission securely on this Mac.

    You doApprove renewalYou seePermission saved

  3. Macos

    Confirm the service is On

    Check the actual status in Settings. If permission is needed, review SWEG Console in System Settings → General → Login Items, then refresh Console.

    You doBackground permissionYou seeOn

  4. Background

    Let Console keep it current

    When this Mac is online and the service can run, Console checks for a due renewal and updates the license for the same device.

    You doAutomatic renewalYou seeLicense updated

What you get

An enabled background service can renew the license while Console’s GUI is closed or signed out.

Keep in mind

Your Mac needs internet access and permission to run the background service. Sleep or offline periods can delay renewal. Switching it Off keeps the current license in place.

Stay licensed · Your Choice

Renewing manually

You can renew without relying on automatic background scheduling. Choose the route that matches your device’s connectivity.

  • Same seat retained
  • Online or file exchange
  • 2 routes
All scenarios

Online

  1. Online Route

    Use Refresh with permission

    If this device already has saved renewal permission, connect to the internet and use Refresh in Console. A due license can renew without opening a browser.

    You doRefreshYou seeCheck renewal result

  2. Status

    Read the result

    Check whether the license was renewed. “Not due” means no refresh is needed in the current daily window. If renewal permission is missing or expired, approve it again or use the file-exchange route below.

    You doRenewal resultYou seeNot due / renewed

Offline or without renewal permission

  1. Offline Alternative

    Export for the existing target

    Save this device’s request. On a connected device, open its existing seat’s Licensing panel, load the matching request, and choose Authorize + export.

    You doExisting seat requestYou seeSigned license

  2. This Device

    Import the renewed license

    Bring back and import the returned .json file. Verify success and the new expiry. Do not deactivate an existing seat just to renew its license.

    You doImport licenceYou seeExpiry updated

What you get

Successful renewal updates the authorization for the existing device seat.

Keep in mind

The file-exchange route is also available when background renewal is Off or unavailable. An online Refresh cannot enroll missing renewal permission by itself. Repeated refreshes do not override the daily issuance limit.

Change devices · Planned Transfer

Moving to a new device

If every seat is in use, release the device you are replacing before authorizing the new one, or add a seat instead. An unused seat can be activated directly.

  • 3 transfers / rolling 180 days
  • +1 per added seat
  • 4 steps
All scenarios

  1. Current Seats

    Choose the right device

    Connect Console, select the product, and check the device label and remaining transfer allowance. If the allowance is exhausted, contact support before proceeding.

    You doReview devicesYou seeCorrect target

  2. Old Device

    Deauthorize its seat

    Use Deauthorize on the current device, or Revoke for a different device. Confirm the operation and wait for the server result.

    You doDeauthorize / RevokeYou seeRelease confirmed

  3. Seat Available

    Confirm the seat is available

    Wait for the released seat to appear as available. Each customer-initiated release uses one transfer from this product’s rolling allowance.

    You doSeat availableYou seeTransfer recorded

  4. New Device

    Authorize the replacement

    Connect the owning account on the replacement and choose Authorize, or use Remote Auth if it is offline. Verify the new local license.

    You doAuthorizeYou seeReplacement licensed

What you get

The replacement uses the released seat. A confirmed local deauthorization removes that device’s license.

Keep in mind

A rolling window is not a fixed twice-yearly reset. Releases age out according to their dates. Moving between your own devices does not transfer the purchase to another person.

Change devices · Recovery

Lost or broken device

You can release the server seat without booting or recovering the old device.

  • Old device not required
  • Transfer allowance applies
  • 4 steps
All scenarios

  1. Connected Device

    Connect the owning account

    Use Console on an available supported device, or deactivate the failed device directly from your SWEG account page.

    You doConnect accountYou seeSeat management

  2. Seats

    Identify the missing device

    Select the native product and inspect the other device’s label and seat. Confirm that this is the device you can no longer use.

    You doLost studio deviceYou seeCorrect seat

  3. Server

    Revoke the old seat

    Choose Revoke for that other device and confirm. The product’s transfer allowance applies; if it is exhausted, support can restore it after review without needing the failed device.

    You doRevokeYou seeSeat released

  4. Replacement

    Activate the new device

    Authorize the replacement using the now-available seat, or complete Remote Auth for an offline replacement.

    You doAuthorize replacementYou seeLicense verified

What you get

The old device does not need to be present for you to recover its server seat.

Keep in mind

Revoke releases the device’s seat in your account. It is a seat-management action; it does not remotely erase files from the old device.

Change devices · Local Recovery

Restoring a missing license

If the server still recognizes this device but its local file is missing or invalid, recover that seat instead of consuming a new one.

  • Existing seat reused
  • Device identity must match
  • 4 steps
All scenarios

  1. Library

    Connect and inspect

    Connect Console, select the native product, and refresh. Confirm that its active server seat matches this device.

    You doRefresh seatsYou seeMatching active seat

  2. This Device

    Choose Restore licence

    When Console offers Restore licence, use it to retrieve and verify the signed file for this existing seat.

    You doRestore licenceYou seeExisting seat recovered

  3. Local Status

    Verify the result

    Refresh local licensing and confirm the file is valid. Recovery should retain the existing seat; inspect before retrying if the result was uncertain.

    You doLocal licenseYou seeLicensed

  4. If Unavailable

    Check identity or import

    An offline device can import a matching signed file. After a reinstall or identity change, inspect server seats first; use transfer or support if the old identity no longer matches.

    You doMatching file onlyYou seeVerify before use

What you get

A missing local file can be recovered without allocating an additional seat when the identity still matches.

Keep in mind

Copying a license from another device will not authorize this one. Keep the installation identity intact during recovery. Do not delete profile data or repeatedly deactivate seats to troubleshoot a missing file.

Questions

A few useful details.

Do I need an iLok account or USB license dongle?

Console’s native licensing uses a SWEG-issued signed file bound to the device. This workflow does not require an iLok account, iLok USB, or iLok Cloud session.

Does signing out of Console stop my audio?

The account connection and local product license are separate. A valid signed license continues to authorize the product after Console disconnects or its account connection expires. Automatic renewal can remain enabled after you disconnect your account.

Does the account connection have a time limit?

Console’s account grant lasts at most 30 minutes and is tied to the website sign-in session. Reconnect for account actions when required. That short connection lifetime is separate from the 365-day signed license file.

Will an internet or licensing-service outage interrupt a session?

An activated product checks its license on your device. Losing internet access or a failed renewal does not interrupt your session or remove the existing license. You can check its status in Console when you reconnect.

Can I run a product on more than two devices?

Yes. Every purchase includes two seats, and you can add seats to that product one at a time from your account. Each added seat is one more simultaneous device and one more transfer. Seats belong to the product they were bought for and do not move between products.

What happens if I return an additional seat?

An additional seat is its own order with its own 14-day refund window. If the return reduces your occupied capacity, you choose which devices are affected, and only enough activations are released to fit what remains. While a request is pending, new activations pause but renewal continues.

Can I use AU and VST3 on the same device?

Yes. Native formats of a product, such as AU and VST3, share one installation identity and one seat on that device. A Max for Live edition is a separate product with its own licence and seats; this guide does not describe its activation workflow.

What does the annual license check-in mean?

A check-in refreshes the license file for your existing device seat. Each refreshed file has a 365-day renewal window. Use automatic renewal, or refresh manually online or by file exchange. This is license maintenance for your perpetual purchase.

What if a license check-in is overdue?

Console shows a renewal reminder. Perpetual licenses have a 60-day grace period; if renewal is still overdue, the matching signed license already on the device continues to support full use, including reopened projects. Renew when you can to keep the file current. Trials and beta access retain their own expiry dates.

What if export fails after authorization?

A seat may already have been allocated. Inspect the server seats before retrying. If the Remote Auth panel still holds the verified license, use Save licence again. Cancelling a submitted request does not guarantee that seat allocation was cancelled.

What if every seat is used, or I reach the transfer limit?

Release an old seat before authorizing another device, or add a seat to that product. Each product allows three customer-initiated transfers in a rolling 180-day window, plus one per additional seat. If the allowance is exhausted, contact support through your SWEG account rather than retrying; it can be restored after review.

Does a reinstall always preserve the seat?

Only a matching device and installation identity can reuse its existing activation. Keep profile data where possible, then inspect the server state. A recreated identity or major hardware change may need recovery, transfer, or support.

Do Device Passes, trials, and beta access follow the same rules?

Do not assume so. Trials and beta entitlements expire at their own date and do not receive perpetual grace. A Device Pass or a visible download is not by itself evidence of a native paid activation or a permanent product license.