Platform - How Celerity Works

The Problem

Why Traditional Ed-Tech Deployments Fail

Districts face the same six barriers every time they try to stand up modern education infrastructure.

Months to Deploy

Traditional Ed-Fi and ed-tech implementations take 6–12 months of planning, procurement, and configuration before a single record flows.

Specialized Staff Required

You need Linux admins, database engineers, and DevOps specialists just to stand up and maintain the stack. Most districts don't have them.

Hidden Infrastructure Costs

Cloud hosting, monitoring, backups, SSL certificates, patching—the true cost of ownership far exceeds the initial license fee.

Security & Compliance Burden

FERPA compliance, vulnerability scanning, encryption, and access controls fall on your team to implement and maintain continuously.

Integration Chaos

SIS, LMS, assessment, and HR data live in separate silos. Normalizing them into a single semantic model is a project in itself.

Lock-in

Proprietary platforms trap your data behind closed APIs. Migration costs make it nearly impossible to switch once you're committed.

The Solution

Celerity Platform Capabilities

Every barrier above has a direct answer in the Celerity platform.

Fast Automated Deployments

Request a supported environment from the web Console and follow deployment and health status without operating the container runtime directly.

Analytics for Education

Lightdash comes pre-connected to your ODS. Beautiful dashboards and data exploration out of the box—no BI team required.

Cybersecurity Scanning

Wazuh SIEM and endpoint detection is built in. Continuous monitoring, automated reporting, and real-time threat detection from day one.

Data Interoperability

Normalize SIS, LMS, and assessment data into a single Ed-Fi semantic model. One API, one data standard, zero integration chaos.

Enterprise Reliability

Automated backups and documented recovery checks support the declared lifecycle for pilot-supported releases.

Zero Lock-in

100% open-source stack. Your data stays with you. Export everything, anytime. No proprietary formats, no exit fees.

Under the Hood

How the Platform Works

A distributed architecture that deploys and manages software across your infrastructure — from a single web interface.

Web Console

Sign in, browse the catalog, and deploy stacks with one click. The console sends your selections to the controller — no CLI, no SSH, no config files.

Controller

The orchestration layer. Receives authenticated deployment commands, manages enrolled nodes, distributes software configurations, and records health across your cluster.

Nodes

Edge agents running on your servers (on-premise or cloud). Each node executes commands from the controller, runs Docker containers, reports health metrics, and auto-updates.

Deployment Flow

You choose a stack from the catalog — like Ed-Fi 7 Standard or Wazuh SIEM. Each stack is a pre-tested bundle of containers, configurations, and health checks.

The controller translates that into commands — which containers to pull, what environment variables to set, which ports to expose, and what health checks to run.

Nodes execute and report back. Containers are pulled, started, and verified. The node agent continuously monitors CPU, memory, disk, and container health — reporting status back to the controller every 2 minutes.

You see it all in the console. Real-time deployment status, node health, container logs, and resource usage — all from your browser. No SSH required.

Authenticated Control Plane

Controller and Node requests use encrypted transport and scoped authentication. Secret material is resolved through the managed secret boundary rather than embedded in catalog manifests.

On-Premise or Cloud

Nodes run on Ubuntu servers wherever you need them — your data center, AWS, Azure, or a server under your desk. The controller manages them all the same way.

Versioned Stack Library

Catalog entries identify versioned integration targets. Runtime-certified and pilot-supported labels appear only when current lifecycle evidence exists for that exact version.

One-Line Install

Adding a node to your cluster is a single curl command. The install script handles dependencies, configuration, and enrollment automatically.

Governance

Pilot Platform Agreements

Two levels of partnership designed to move you from discovery to production without the typical legal bottlenecks.

1. Pilot Agreement

Designed for rapid evaluation and data discovery. Focuses on the 30-90 day pilot period with minimal legal overhead.

✓Rapid deployment authorization
✓Initial data processing terms
✓Evaluation support included
✓P-Card friendly billing

2. Production Enablement

Full enterprise governance for long-term production operations. Transitions your pilot environment into a permanent institution asset.

✓Master Service Agreement (MSA)
✓Availability terms defined in the customer agreement
✓Enterprise support & account management
✓Multi-year pricing protection

How It Works

Three Steps to a Pilot

Scope the target, deploy a supported version, and verify the declared lifecycle evidence.

Sign Up

Create your account and start a 30-day pilot. Select your agreement level — start with a Pilot Agreement for evaluation or Production Enablement for immediate scale.

Deploy

Select your stack and hit deploy. Celerity auto-provisions your ODS/API, Admin App, analytics, SSO, security scanning, and backups in days.

Connect

Point your SIS at the API, import your data, and see analytics immediately. Your education data platform is live.

Enterprise Ed-Tech in Days, Not Months.