Licences, domains and renewals

Until then you can activate an install from the command line. Pipe the key in so it stays out of your shell history: cat key.txt | php artisan psa:license:activate --stdin. Then run php artisan psa:license:status to see the licence state, its domain and its updates-until date. The status command never prints the key.

You buy CVN PSA once. The licence is perpetual: your install keeps working for as long as you run it. The price includes one year of updates and support.

What you get

• The full product, every module, with no per-technician or per-client fees.
• One year of updates and support from the day you buy.
• One production domain and one staging domain.
• Releases as readable PHP, apart from the licence-checking code, which is obfuscated. The licence and the EULA set out how you may use the code.
• Full white-label: your brand on every screen your staff and clients see.

Prices are in Canadian dollars.

Your account

Your licences live in your account at account.cvntechnologies.com. An account belongs to your organisation and can have several logins:

• Owners and admins can buy, renew and move domains.
• Members can download releases and open support tickets.

Each licence shows its key, its domains and its updates-until date.

Domains

Production

The installer redeems your licence key and binds the licence to your production domain. The licence file on your server is signed and names that domain.

To move to a new domain, change it from your account. The old domain is released, and the change is logged.

Staging

You can name one staging domain, such as staging.helpdesk.your-msp.com, in your account. It runs alongside production without replacing it. The staging domain cannot be the same as the production domain.

Local and test hosts

These never count as a domain and never bind the licence:

• localhost, 127.0.0.1 and ::1
• any name ending in .localhost, .test or .local

Use them freely for development and testing.

Check-ins

Your install checks in with your account once a day, and again when it looks for updates. A failed check-in never affects the running install. There is no switch that turns your install off.

Updates

A release is yours to install if it was published on or before your updates-until date. That stays true after your update year ends: you can install any release from your year at any time.

Releases published after your updates-until date need a renewal. The updater lists them as "updates expired on (date), renew". See Updates and renewals.

Renewing

A renewal adds one year of updates and support.

• If your update year has not ended, the new year is added to the end of it. You lose no days by renewing early.
• If it has ended, the new year starts on the day you renew.

When the update year ends

Support

Open support tickets from your account. Support is included while your update year is active.