Skip to content

Licensing

Two ways to run Mirket LMS. Same product either way.

Every installation serves one organization — yours. The two deployment models differ in who operates the infrastructure, never in what you get.

One product, two operating models

The product stays complete; responsibility for operation changes.

  1. Same product
  2. On-premise license
  3. Managed service

The same product is available with an on-premise license or a managed service; operating responsibility changes while the product stays the same.

Licensing

On-premise license

You run the data plane.

Mirket is installed on infrastructure your organization owns or rents. Your policies govern storage, backups, authorized exports, and downloads within that operating boundary.

Best for: Organizations with an internal operations team, or a regulatory position that requires data to remain on named infrastructure.

What each offering includes

  • Annual license for one organization, one installation
  • Container images for the API, workers, real-time services, and the enabled role applications
  • Reference deployment: PostgreSQL, Redis, object storage, and collaboration services
  • Operator manual covering installation, upgrade, backup, and recovery procedures
  • Versioned upgrades for the duration of your maintenance term

Priced per organization once we know your size, deployment shape, and support term.

Schedule a demo

or email hello@mirket.dev

Mirket-managed service

Mirket operates the data plane.

The same product, operated by Mirket on a dedicated instance. Your organization still gets its own isolated runtime, database, and storage — managed operation does not mean sharing.

Best for: Organizations that want the product without staffing infrastructure operations, and are able to place learner data with a processor.

What each offering includes

  • Annual service for one organization on a dedicated instance
  • Isolated runtime, database, and object storage — never pooled with another organization
  • Provisioning, monitoring, patching, and version upgrades handled by us
  • Managed backups with an agreed retention and restore target
  • Named support contact and an agreed response window

Priced per organization once we know your size, deployment shape, and support term.

Schedule a demo

or email hello@mirket.dev

Licensing

Where the models differ.

Four operational questions separate them. Everything else is the same product under the same isolation model.

Who operates the data plane
On-premise license Your operations team
Mirket-managed service Mirket, on a dedicated instance
Where organization data lives
On-premise license Infrastructure you control
Mirket-managed service A region agreed with you
Upgrades
On-premise license You schedule and apply them
Mirket-managed service Applied by us on an agreed window
Backups
On-premise license Your backup policy and retention
Mirket-managed service Managed, with agreed retention

Licensing

Included in both models.

There is no reduced edition. Choosing managed operation does not remove capability, and choosing on-premise does not remove support.

  • One organization per installation — no shared tenancy in either model
  • Core learning, assessment, planning, administration, and reporting, plus the optional modules included in the agreed deployment
  • Student, Instructor, and Administrator applications, with an optional Parent browser portal and role-scoped permissions
  • The public user manual, and an interface published in every language this site lists
  • Organization-scoped storage with signed delivery rather than public object URLs

Licensing

Before you get in touch.

Why is there no price on this page?

Both offerings are scoped to an organization: the number of people, the deployment shape, and the support term all change the figure. We would rather give you an accurate quote than a headline number that does not survive the first conversation.

Can we start with a managed instance and move on-premise later?

A move can be planned because both models use the same product and data model. Agree the export, hand-over, timing, and validation steps before signing so the migration boundary is written into the contract.

Does managed operation mean our data is pooled with other organizations?

No. A managed instance is dedicated: separate application processes, database, and storage namespace. The isolation model is identical to an on-premise installation — the difference is who operates it.

What about learners under 18?

Mirket is built for organizations whose learners include minors, which is why the data plane is organization-scoped in both models and learning files use exact-context access policies. Bring your data protection requirements to the first sales conversation so the deployment shape is decided with them in view.

See how Mirket LMS fits your organization.

Book a guided demonstration to explore the product and discuss deployment and licensing for your organization.

or email hello@mirket.dev

Schedule a demo