Choose where Constructor Platform runs

Constructor Platform Installer deploys the full platform onto infrastructure you or your customers control, so data stays where your rules require it. You get the same apps as in our cloud, with regular updates.

Any public cloud

Global providers, or local and national clouds that meet a country's sovereignty rules. Your account, your region, your data.

On-premise

Install onto servers in the customer's own data center, for security, sovereignty, or procurement rules that require owned infrastructure.

Partners install it for customers

Some customers must run the platform on their own infrastructure, because of regulation, a tender requirement, or their security policy, but don't want to build their own platform team. A local partner can install and run it for them.

You install it and apply each new release

Set it up on your customer's servers as a single-tenant installation.

Customers get on-premise without building a platform team

They meet their on-premise rules with the support of a local partner.

Installation and updates become services you sell

Sell them alongside the licenses and stay in touch with every customer.

One organization or many

Choose a single-tenant setup for one customer, or a multi-tenant setup for customers and partners serving many organizations.

Many organizations (multi-tenant)

For partners serving customers in their region. One installation serves many customer organizations. Each customer gets its own isolated organization on its own subdomain, and the partner operates one platform for all of them.

One organization (single-tenant)

For customers. An institution installs Constructor Platform for itself only, as one organization on its own domain.

What gets installed

Constructor Platform plus the apps you choose

Constructor Platform is always installed. It provides administration, users, and shared services.

On top of it, choose the apps: Proctor, Learn, Prism, Assess, Practice, Groups, Hypothesis, and Schedule. The Installer shows the resources each one needs, and you can add more apps after the first installation.

Choosing Constructor Platform apps in the Installer, with the resources they need

How it works

One tool takes you from first setup to every update

1. Run the Installer

Use the guided desktop app, or the command line for scripted and repeatable installations.

Constructor Platform Installer welcome screen

2. Choose apps and configure

Choose the apps, then enter the infrastructure and configuration details: the deployment domain, certificate, outbound email, and the first administrator account.

Configuring the deployment domain and certificate in the Installer

3. Review and start the installation

Check the selected apps, the resources they need and your configuration, then start the installation.

Reviewing the selected apps and configuration before installation

4. The Installer does the rest

The Installer sets up Kubernetes, the database, and the platform, then installs each app you selected.

The Installer setting up Kubernetes and installing the platform

5. Sign in and stay current

Sign in as the first administrator and finish setup in the admin panel. When Constructor publishes a new release, the Installer updates the installed apps, adds any apps you choose, and updates itself.

Constructor Platform sign-in screen after installation

Documentation and support

Request access

partners-icon-download

Partners get the Installer by email

We match your business email with our partner records and send recognized partners the Installer and the installation guide.

partners-icon-message-square

Everyone else hears from our team

Not a partner yet? Our team contacts you to discuss your deployment and the right way to install it.