DivisionOS is the console for the Aptik suite

Bring your people in once, and send them to every app that needs them.

Import students and staff from a CSV, Clever, Microsoft School Data Sync, Entra ID or Google Workspace. Shape them into groups, send each group to the apps that use it, and open every Aptik app from one place.

See the demo Sign in

10: Aptik apps, opened from one place
Dry run: First, before anything is written
No deletes: People who leave are switched off

control.aptik.io/orgs/meridian

Meridian Unified School District

Sources

CleverDirectory sync
Microsoft School Data SyncDirectory sync
Microsoft Entra ID groupsDirectory sync
CSV upload (OneRoster)Upload a file

Groups

Grade 6 students
Front office staff
Bus drivers and aides
Examples

Apps

CompassReceives groups
TransmitReceives groups
AssemblySubscribed

Sources, then groups, then apps. Group names are examples; the rest is the seeded demo district.

Previewed first

Nothing is written until you have seen it.

Nobody is deleted

People who leave are switched off.

One sign-in

The same account across the suite.

Works on its own

Every app runs without DivisionOS.

The suite

10 apps, opened from one place

VenueFacility rentals
PodiumWebsites & CMS
TransmitMass notifications
AssemblyGradebook & classroom
FolioFinance & ERP
EmpowerHuman resources
CompassForms & workflow
BlueprintMaintenance & assets
AlignContracts & compliance
PulseStudent & guardian portal

What it does

Your people, your apps and your subscriptions in one console

A district is one customer across every Aptik app. DivisionOS is where its people come in, where they are grouped, and where each app is opened from.

Bring your people in once: Upload a CSV and say what its columns mean, with checks for problems and duplicates, or connect Clever, Microsoft School Data Sync, Entra ID or Google Workspace groups. Anyone who leaves a source is marked inactive, never deleted.
Shape them into groups: A group can follow a filter, such as every Grade 6 student at one school, or be a saved list. Preview who is in a group before you save it.
Send each group to the apps that need it: Compass and Transmit receive groups today, with the columns you choose. Every send is checked with a dry run first, and in mirror mode people who leave a group are switched off in the app, not deleted.
Open every app from one place: Each Aptik product your district subscribes to has a tile, with its status: subscribed, trial ends in so many days, or not subscribed. The tiles come from your subscriptions, so there is no second list to keep up.
Subscriptions and shared connections: Seats, trials and renewal dates in one table, and which connection each app actually uses: the district's shared one, its own, or none. Connect Stripe once for the whole district and give a single product its own account when it needs one.
Roles that are enforced: Owners, IT, executives and members each see what their role allows. Only an owner may change a subscription, and that rule is enforced on the server, so it holds for anything calling it, not just this interface.

Subscriptions

What the district subscribes to, at a glance

Seats, trials, renewal dates and which connection each app uses. Usage is not metered and nothing is invoiced here, so no figure for either is shown.

Open the demo

Products: 10; 2 of them still on trial
Seats: 9.0k; Across every per-seat product
Credentials: 8; Providers connected, none held here
Next renewal: 14 days; The soonest date on the account

Seats by product

Per-seat products only. Podium covers a whole district, so it has no seat count.

What needs attention, and when

Renewals and trial ends, by how far out they are.

How the credentials resolve

Most specific wins: an app's own key, then the district's, or none.

How it works

Set it up once, and no app depends on it to run

The third step outranks the other two. Every app in the suite works without DivisionOS, and without any other app. DivisionOS adds to what an app can do; it never takes a product away. Taking a payment is the one deliberate exception, because there is nothing safe to fall back to.

1
Bring your people in
Connect a source or upload a CSV. Every import and sync is previewed first, so you see who would be added, updated or switched off before anything is written.
2
Group them and send them
Make a group, choose the app and which columns to fill. A dry run shows exactly what would change in the app; applying it is a separate step.
3
Every app keeps working regardless
DivisionOS can add capability to an app, never take it away. If it cannot be reached, an app carries on with the last answer it had, and a district running one product on its own sees a fully working product.

Security

It holds your people and your connections, so it is careful with both

DivisionOS is deployed apart from the other apps on purpose. It holds the connections every app shares, and that calls for a different level of care from any one product.

Previewed before anything is written: Imports, source syncs and sends to an app all show what would change first. Applying is a separate step, so nothing happens to your records by surprise.
Nobody is deleted from an app: A person who leaves a group or a source is switched off or marked inactive. Records stay, so a mistake in a filter can be undone.
Keys are never shown back: A connection shows its status and the last few characters of its key, not the key. Payments are made through DivisionOS so an app never holds the credential.
One sign-in across the suite: Every product signs in to the same account system, so a person who can sign in to one is the same person here. Your district's records are visible only to its own members.

The demo is the portal’s own screens over the seeded demo district. No sign-up.

See the demo Sign in

Bring your people in once, and send them to every app that needs them.

Aptik apps, opened from one place

Dry run

First, before anything is written

No deletes

People who leave are switched off

Your people, your apps and your subscriptions in one console

A district is one customer across every Aptik app. DivisionOS is where its people come in, where they are grouped, and where each app is opened from.

Bring your people in once

Upload a CSV and say what its columns mean, with checks for problems and duplicates, or connect Clever, Microsoft School Data Sync, Entra ID or Google Workspace groups. Anyone who leaves a source is marked inactive, never deleted.

Shape them into groups

A group can follow a filter, such as every Grade 6 student at one school, or be a saved list. Preview who is in a group before you save it.

Send each group to the apps that need it

Compass and Transmit receive groups today, with the columns you choose. Every send is checked with a dry run first, and in mirror mode people who leave a group are switched off in the app, not deleted.

Open every app from one place

Each Aptik product your district subscribes to has a tile, with its status: subscribed, trial ends in so many days, or not subscribed. The tiles come from your subscriptions, so there is no second list to keep up.

Subscriptions and shared connections

Seats, trials and renewal dates in one table, and which connection each app actually uses: the district's shared one, its own, or none. Connect Stripe once for the whole district and give a single product its own account when it needs one.

Roles that are enforced

Owners, IT, executives and members each see what their role allows. Only an owner may change a subscription, and that rule is enforced on the server, so it holds for anything calling it, not just this interface.

Bring your people in once, and send them to every app that needs them.

10 apps, opened from one place

Your people, your apps and your subscriptions in one console

What the district subscribes to, at a glance

Seats by product

What needs attention, and when

How the credentials resolve

Set it up once, and no app depends on it to run