Every student covered.
Every school isolated.
Covera unifies paraprofessional scheduling into one shared core with two swappable views, real per-user accounts, and row-level isolation so no school ever sees another school's data.
Lincoln High
Today's coverage
Trusted by student services teams across pilot districts
Everything a para team needs, nothing they don't
Rebuilt from a clean slate as one shared, secure SaaS core, so every school runs the same reliable system.
One core, two views
The block-grid and timeline layouts read from a single schedule model. Switch views without duplicating a single row of data.
Tenant isolation by design
Row Level Security enforces school boundaries at the database, not in application code. A query can never cross a tenant line.
Real per-user accounts
Individual authenticated logins replace the shared password. Every action is attributable to a named staff member.
Auto-provisioned onboarding
A paid checkout spins up a fully isolated school workspace in seconds, seats included, zero manual setup.
Live coverage tracking
Gaps surface the moment a para is pulled. Fill an uncovered block before a classroom ever notices.
Built for para teams
Roles, rooms, 1:1 assignments and lunch duty modeled the way schools actually run their support staff.
The same schedule, two ways to see it
Switch schools to watch the board isolate to a single tenant, then flip between the block-grid and timeline layouts. Nothing is entered twice.
Lincoln High School
District plan · 214 students supported
95%
Day coverage filled
6
Paraprofessionals on shift
40
Blocks assigned today
2
Uncovered gaps to fill
Alicia Moore
1:1 Aide
Devon Blake
SPED Para
Priya Nair
Behavior Tech
Carlos Vega
Inclusion Aide
Sarah Whitfield
Float Para
Marcus Reid
SPED Para
A wall between every school, enforced at the data layer
Isolation is not a setting you can forget to turn on. Row Level Security binds every record to its school, so a query simply cannot return another tenant's rows. Then a dedicated QA pass proves it.
Policies at the row
Every table carries a school_id and an RLS policy. The active session can only read and write its own rows.
Verified, not assumed
A dedicated QA pass probes every endpoint with cross-tenant tokens to prove data never leaks between schools.
Scoped sessions
Auth issues a school-scoped session on login, so isolation follows the user through every request automatically.
Lincoln High
school_id scoped
Maple Grove
school_id scoped
Riverside Prep
school_id scoped
create policy "tenant_isolation"
on coverage_blocks
using (
school_id = auth.school_id()
);
-- QA: cross-tenant token → 0 rowsPayment in, isolated school out
A verified Stripe webhook provisions a brand new, fully isolated school workspace the moment a payment clears. No manual setup, no waiting on ops.
School pays
A new school completes Stripe checkout for the plan and seat count they need.
Webhook fires
A verified Stripe webhook lands and provisioning kicks off automatically, no ops ticket required.
Isolated tenant created
A fresh school workspace is created with its own RLS boundary and an owner invite.
Team logs in
Staff accept individual invites and start scheduling on day one with real per-user access.
99.98%
Coverage uptime across pilots
0
Cross-tenant records in QA audit
2
Schedule views, one data core
<30s
From payment to live workspace
Loved by the people who run coverage
We stopped juggling five separate logins and spreadsheets. One board shows every para, every gap, every day, and I trust our data never touches another school.
Diane Whitmore
Director of Student Services, Lincoln High
The switch from a shared password to real accounts alone was worth it. Now I know exactly who moved a coverage block and when.
Marcus Reid
SPED Coordinator, Riverside Prep
Our grid people and our timeline people finally use the same tool. Same data, their own view. No more reconciling two systems.
Sarah Whitfield
Operations Lead, Maple Grove
We signed up on a Friday and the whole team was scheduling by Monday. No setup calls, no migration, it was just there.
James Okafor
Assistant Principal, Cedar Ridge
Priced per school, isolated by default
Every plan includes both schedule views, real accounts, and row-level tenant isolation. Scale from one building to a whole district.
Single Site
One building, fully isolated, up to 30 staff seats.
- Both schedule views
- Live coverage gap alerts
- Per-user authenticated accounts
- Row-level tenant isolation
- Email support
District
Multiple buildings under one district, each isolated.
- Everything in Single Site
- Unlimited staff seats
- Auto-provisioned new schools
- Cross-building admin roles
- Priority support & QA reports
Enterprise
Statewide rollouts with security review and SSO.
- Everything in District
- SSO & directory sync
- Dedicated isolation audit
- Custom data residency
- Named success manager
Answered before you ask
Every record carries a school identifier and a Row Level Security policy at the database level. A logged-in session can only ever read or write rows belonging to its own school, so isolation is enforced by the data layer itself rather than trusting application code.
It is gone. Each staff member gets their own authenticated account with a named identity, so every schedule change is attributable and access can be revoked per person without disrupting the team.
The block-grid view lays staff against time slots in a dense board, ideal for spotting coverage at a glance. The timeline view shows each person as a continuous lane. Both render from the exact same schedule data, so nothing is ever entered twice.
When a school completes checkout, a verified payment webhook automatically provisions a brand new isolated workspace with its own boundary and an owner invite, typically in under thirty seconds and with no manual steps.
Covera starts you on a clean, shared multi-tenant core. New schools begin fresh, and we can advise on importing prior schedules where it makes sense.
Bring every school onto one secure board
Start a free trial today, or talk to us about a district rollout with a dedicated tenant-isolation audit.
