ClassCore, under your institution's control.

Deploy ClassCore within an institution-controlled environment when data location, infrastructure ownership or local policy requires a dedicated installation.

Plan an on-premise reviewSee the deployment model
Institution-specific architecture, mutual NDA and a license limited to the named institution or approved chain.
Institution data boundaryArchitecture draft
Application services
Web UIAPI gatewayBackground jobsNotifications
ClassCore platform
AcademicFinanceWorkflowsIntegrations
Data layer
PostgreSQLFile storage
Primary environmentRegistrar-controlled copyInstitute server copy
01

Control begins with a deployment model everyone can explain.

ClassCore works with your IT and governance teams to define the environment, identity, network, database, backup, monitoring and support model before sharing a custom quote. The agreed license is issued only for the named institution or chain and cannot be resold or extended to unauthorised institutes.

Deployment model

Architecture, license and responsibility—agreed together.

An on-premise quote follows discovery because the technical boundary and operating responsibilities change the work.

01

Mutual NDA

Protect the infrastructure, data and operating information exchanged during discovery and implementation.

02

Named license

License the installation only to the named institution or approved chain. Resale or use by other institutes is not permitted.

03

Custom quote

Price the actual environment, integrations, migration, resilience, support and rollout—not a generic server bundle.

Configurable resilience

Place independent copies where your approved design needs them.

ClassCore can help evaluate a primary AWS or Azure environment, a registrar-controlled copy and an institute-server copy. The exact retention, encryption and recovery route is documented for each deployment.

Primary environmentAWS, Azure or institute serverRegistrar-controlled copyOptional independent backupInstitute server copyOptional local copy
02

Choose the operating boundary that fits.

The exact design is confirmed during discovery; these are the deployment paths ClassCore can help you evaluate.

01Institute server

Run ClassCore inside your own infrastructure.

Install the application and data services within an institution-controlled private environment.

  • Private network
  • Institution identity
  • Local operations
ClassCore · Institute server
Live institutional contextEnvironment · On-premise
Private networkReadyInstitution identityConnectedLocal operationsIn context
Institutional control

A dedicated ClassCore environment with the operating boundary, responsibilities and license made explicit.

03

A controlled rollout with visible gates.

Architecture, responsibilities and evidence are agreed before production data moves.

01

Discover

Map requirements and constraints.

02

Design

Agree architecture and ownership.

03

Install

Provision and configure the platform.

04

Validate

Test function, performance and recovery.

05

Handover

Train teams and document operations.

04

Security is a shared operating discipline.

ClassCore secures the application; your team governs the surrounding institution-controlled environment according to the agreed model.

01

Named data boundary

Document where application services, databases, files and backups live.

02

Shared responsibility

Assign identity, network, patching, monitoring and recovery ownership before go-live.

03

Restricted license

Use the installation only for the named institution or approved chain; resale is not permitted.

04

Evidence and continuity

Retain architecture, validation, runbooks and recovery evidence for ongoing operations.

C

Design the right deployment before choosing the hardware.

Bring your IT, data-location and policy requirements. We will map the architecture and prepare a custom quote.

Plan an architecture review Review security