Every school. One platform.
One invoice.
Three schools or three hundred — every one on a single accessible, monitored, fully managed platform, websites and native mobile apps together, while each school keeps its own name, its own look, and its own domain. Thirteen years building for New York schools.
Request the free audit Check your complianceSend us your list of school websites. We'll tell you which ones fail accessibility, which are broken on phones, and what it would take to fix all of them.
District DashboardOne alert.
Every school. Instantly.
Every school keeps its own look. The notice is one shared entry — edit it once and all of them are correct.
ADA Title II now sets a hard technical standard for school websites — and mobile apps.
The Department of Justice's 2024 rule requires web content and mobile applications of state and local government entities, including public school districts, to conform to WCAG 2.1 Level AA . Compliance was due April 2026 for districts serving populations of 50,000 or more, and is due April 2027 for smaller districts and special district governments.
Most school-site vendors treat accessibility as a statement page. It is now a technical specification, it explicitly covers your apps as well as your sites, and it applies to every one of your schools — including the ones your district office doesn't manage.
Request the free auditEvery school a different system. One liability.
Nobody knows what's out there
Some schools are on a vendor. Some are on a CMS a parent volunteer set up. One hasn't been updated since the principal who had the password retired. The district is responsible for all of them and has visibility into none of them.
Every school buys separately
A website contract per school, an app vendor per school, a renewal date per school, a support queue per school — and no purchasing leverage in any of them. The district pays retail over and over.
The exposure is district-level
An accessibility complaint, a compromised site, a missed closure notice, a wrong translation on an emergency alert — none of those land on the school. They land on you.
The objection we hear firstConsolidated. Not homogenized.
This is where district website projects usually fall apart: the district wants one platform, and every principal hears "our school is about to look like everyone else's." On our platform they don't have to.
Six genuinely different designs
Each themed with about fifty design tokens. Different structure, different typography, different color — two schools on the same platform can look nothing alike.
Every school keeps its own domain
Their web address doesn't change. Their email doesn't change. We never touch their name servers.
Every school keeps its own admin
The people who update the site today keep updating it. Nobody has to route a lunch menu change through the district office.
Every school keeps its own features
A high school can run forms and photo galleries; an elementary school can turn off what it doesn't use. Content and navigation are theirs.
What the district gets is not uniformity. It's a floor — every school accessible, fast, backed up, monitored and current — under one contract.
One announcement. Every school. Instantly.
District alerts
Post a closure, a delay, or an emergency notice once. It appears in the alert bar on every school's website and app, ahead of that school's own notices. One edit updates all of them; one delete clears all of them.
One district calendar
Publish the district calendar once — holidays, professional development days, testing windows, half-days — and it merges chronologically into every school's calendar, labeled as a district date. Parents see one calendar, not two they have to reconcile.
The detail that matters operationally
These are shared entries, not copies. When a snow day moves, you change one record and every school is correct. Platforms that fan out copies leave you chasing each school separately to fix one date — and one of them always gets missed.
District notices never overwrite a school's own alerts and events — they sit alongside them, so schools keep their own voice. District-wide push notifications are on our roadmap for this platform.
Clear lines about who can change what.
What each role can do on the platform Role Can do District administrator Publish district-wide alerts and calendar dates; see every school; manage membership and settings School administrator Everything within their own school — and nothing outside it Staff Read the private staff area at their school (optional per school) Families and the public Read the public site. No accounts, ever.Enforced in the database, not the interface
Most platforms hide the buttons a user shouldn't press. We enforce the boundary at the data layer — a school administrator cannot reach another school's content even with developer tools open. District content is district-writable only.
And it's all on the record
Every administrative change across every school is written to an append-only audit log: what changed, when, and by whom. When a district asks "who deleted that page?", there is an answer.
WCAG 2.1 AAAccessible by construction. Verified by machine. Across every school.
Built in, not bolted on
Semantic structure, visible keyboard focus, labeled controls, live regions on loading and error states, and contrast-safe color pairs that hold no matter which brand colors a school picks — a principal cannot choose their way into a contrast failure.
Your apps are covered too
The 2024 rule covers mobile applications explicitly. Because our apps and websites are one platform, an accessibility fix ships to both at once. Districts running a website vendor and a separate app vendor have two compliance surfaces and two vendors pointing at each other.
We can prove it on demand
There's an automated check suite built into the platform that runs against your live sites — accessibility basics, page rendering, error states, forms, permissions and data integrity. Not a pre-release test on our machines: a test we can run on your production sites, on the call, and send you the output.
Ongoing, not one-time
Regressions happen when a school uploads a bad image or publishes an unstructured page. Checks run continuously, and the design system prevents most of the common failures from being possible in the first place.
The translate widget most districts are running is itself an accessibility failure
The stock website-translation widget schools bolt on fails audit — unlabeled dropdown, untitled frames, low-contrast chrome. It is one of the first things a WAVE or axe scan flags, and it is frequently the reason a site that "looks fine" fails. We suppress it entirely and ship our own accessible control.
Request the free audit36 languages. Every page. Every school.
One control, in each language's own script, with right-to-left support — on every page of every school in the district, including forms and emergency alerts.
Español 中文(简体) 中文(繁體) বাংলা العربية Kreyòl Ayisyen Русский 한국어 اردو پښتو دری Hmoob Soomaali አማርኛ नेपाली Українська Tiếng Việt Shqip ਪੰਜਾਬੀ ગુજરાતી हिन्दी ខ្មែរ မြန်မာ ไทย 日本語 Filipino Português Polski Français Deutsch Italiano Ελληνικά עברית Türkçe Kiswahili EnglishFor districts with translation obligations under state or federal language-access rules, this is the difference between a compliance line item and a checkbox. No per-school setup, no per-page work, and no additional cost per language.
Every school. Not a project per school.
The reason district website consolidations take two years is content migration — every school is asked to rewrite its own site, and half of them never do. We don't ask them.
We import from the sites you already have
Give us the list of school web addresses. We pull the text from each existing site, clean it, and load it into a themed, working site — pages, staff, events, links, contact details. The school reviews it rather than writing it.
Text only, always
Compromised school websites are routine, and a district migration is exactly when malware spreads between properties. Our import takes text and nothing else: every image reference, script, piece of markup and insecure link is stripped before anything is stored. Images are re-uploaded fresh.
Schools review, they don't author
Each school gets a private preview link and a checklist. The lift for a school secretary is an afternoon, not a semester.
Nothing goes dark during the switch
Each school's existing address keeps working, and we cut over when that school is ready — school by school, not all at once.
One screen for the whole district.
Traffic
Across the district and per school — views, visitors, by day and by month.
Engagement, school by school
Views, visitors, form submissions, last content update and last admin login. That last column is how you find the three schools that have stopped updating — before a parent does.
Storage & content
Totals per school, so nobody is surprised by a limit.
Administrator directory
Who has access to what, across every school in the district.
Errors & slow pages
Crashes and performance problems reported by real browsers, grouped so one bug is one row instead of five hundred.
No third-party trackers
Analytics are first-party and stay in your district's data. Nothing sold, shared, or sent to an ad network — one fewer vendor for your privacy officer to review.
Written for your data privacy officer.
No family accounts. No student information system sync. No rosters, no grades, no attendance. Our platform is not integrated with your SIS and does not receive student records. When a school collects information through a form — a registration, an absence report, a permission slip — that submission is stored under per-school database permissions, visible only to that school's administrators, and exportable or deletable on request.
We will sign your district's data protection agreement and complete your review process.
No application server to breach
Authorization is enforced in the database itself. There is no middle tier holding credentials for every school.
Every uploaded file is inspected
Family attachments land in a private area nobody can read, are checked byte-by-byte against their declared type and screened for active content before release. Administrators download through links that expire in sixty seconds.
Forms resist abuse without losing submissions
Rate limiting, bot challenge, server-side validation, and spam scoring that flags rather than deletes . A suspicious registration still appears in the school's dashboard.
Nightly off-site backups
Of the entire platform, plus per-school exports. A single school can be restored without touching any of the others.
An append-only audit trail
Of every administrative change across the district — enough to answer "what changed and who changed it," and enough to put it back.
Your content is yours
Exportable on request, in a documented format. No hostage clause, no per-export fee.
Arrange a briefingWhere districts are today, and where this puts them.
Every row here is something we will demonstrate live on a briefing call.
Comparison of schools buying separately and one district platform Every school buying separately One district platform Contracts One per school, plus app and forms vendors One Renewal dates Scattered across the year One Accessibility Unknown per school; unverified WCAG 2.1 AA by construction, checked against live sites Mobile apps A separate vendor, or none Included and branded per school Emergency alerts Called or emailed school by school Published once, live everywhere District calendar Re-entered by every school secretary One entry, merged into every school's calendar Translation Per-school widget, often failing audit 36 languages, accessible, everywhere Oversight None One dashboard: traffic, activity, storage, errors, admins Backups Per school, if any Nightly, off-site, plus per-school restore Who's responsible when a site breaks Ambiguous Us Migration Each school rewrites its own site We import from the sites you already have Cost Retail, once per school Per school, declining with sizeScroll the table sideways on a small screen.
A semester, not a fiscal year.
- 1
Weeks 1–2
Audit and plan
We scan every school site you have and deliver the report. You pick the pilot schools. Procurement and the DPA run in parallel.
- 2
Weeks 3–4
Pilot
Two or three schools go live end to end — imported, themed, reviewed, cut over. These become the internal proof that wins the remaining principals.
- 3
Weeks 5–10
Waves
Schools go live in batches of five to eight — as many waves as your district needs. Each school gets a preview link, a review checklist and a 30-minute training session. District alerts and calendar switch on with the first wave.
- 4
Week 11 onward
District operations
Full dashboard, monitoring and one support queue. Remaining schools join on their own timetable — nothing is blocked on the slowest school.
What the district office actually has to do
Provide the list of school websites, name one project contact, and approve the design direction. That's it. We don't run a change-management program on your staff.
Built with New York schools, for thirteen years.
500+ school websites and apps built — including branded school apps live in the App Store and Google Play, many of them for New York City public schools. This is not a roadmap. It is work we have been shipping and operating for years.
Live on the App Store Live on Google Play 13 years with New York schools 500+ websites and apps built 36 languages, every page WCAG 2.1 AA by construction 6 designs per school Nightly off-site backupsSchools and districts we already run.
Live sites, right now — including Manhattan HS District, a multi-school district running on this platform today. Click any of them; that is faster than anything we could tell you.
MHSD Manhattan HS District manhattanhsdistrict.org BC BCCSA thebccsa.org PS1 PS1X ps1x.org 223 MS/HS 223 mshs223.org SA SeeAll Academy seeallacademy.com GHS Grady HS gradyhs.com 369 PS 369 ps369.org MHSD Manhattan HS District manhattanhsdistrict.org BC BCCSA thebccsa.org PS1 PS1X ps1x.org 223 MS/HS 223 mshs223.org SA SeeAll Academy seeallacademy.com GHS Grady HS gradyhs.com 369 PS 369 ps369.org 22 JHS 22 jhs22.com 154 PS 154X ps154x.com 179 PS 179 ps179.com 242 PS 242Q ps242q.org CLI Girls in CLI girlsincli.org NY NYS ALAS nysalas.org 544 HS 544 hs544.org 22 JHS 22 jhs22.com 154 PS 154X ps154x.com 179 PS 179 ps179.com 242 PS 242Q ps242q.org CLI Girls in CLI girlsincli.org NY NYS ALAS nysalas.org 544 HS 544 hs544.orgSupporting our education community
NYSALAS Founding Partner OWE-CSA Diamond Partner The Black Caucus Girls Inc. of LI Urban TechPriced per school. One purchase order.
The per-school rate declines as the district grows. Every school in a district plan gets the full platform — there is no cut-down tier.
Small
1–4 schools
Full platform per school, consolidated billing.
Network
5–14 schools
Adds district-wide alerts and the shared calendar.
Most districtsDistrict
15–29 schools
Adds the district dashboard and a named account contact.
Large
30+ schools
Let's talk. Phased rollout, custom terms, procurement support.
Included on every district plan
Website and branded mobile app per school
All content sections and forms
Each school's own domain
36 languages and WCAG 2.1 AA
Nightly backups and monitoring
District alerts and shared calendar
The district dashboard
Content migration from your old sites
Training and support
One purchase order, one renewal date, one invoice. We complete district vendor onboarding, insurance and data-privacy paperwork as part of the contract — not as a change order.
The questions that come up in every district call.
Will all our schools look the same? No — and this is the objection we hear first, so we designed against it. Six genuinely different designs, each fully themed to the individual school, plus each school keeping its own domain and its own admin. Ask us to show you two schools side by side. Our schools each own their own domain. Do they lose it? No. Every school keeps its address, its registrar, and its email. We add two DNS records. We never take over name servers — that's what breaks school email, and it's why districts get burned. What about the schools that don't want to move? They don't have to move on your timeline. Schools go live in waves and nothing is blocked on the slowest one. In practice the pilot schools do the convincing for you. Can our district office publish to every school? Yes — alerts and calendar dates publish district-wide instantly, as shared entries rather than copies. School content stays with the school. Who does the content migration? We do. We import from each school's existing site and the school reviews rather than writes. Text only — we assume some of those old sites are compromised. How do we know this is accessible? Ask us to run our automated check suite against your live sites on the call, and read the output yourself. Then compare it to what your current vendor can produce. Does this connect to our student information system? No, by design. No roster sync, no grades, no attendance — which also means a much shorter data privacy review. What's our exit? Your content exports on request, in a documented format. No hostage clause. We're mid-RFP. Send us the RFP. We respond to district procurement regularly and we'll tell you honestly if we're not a fit.Start with the audit, not the sales call.
Free · No obligation · Yours to keepThe Free District Digital Audit
Send us the list of your school websites. Within two weeks you'll have a report showing which schools fail WCAG 2.1 AA, which are broken or slow on phones, which have dead links and stale content — plus one school rebuilt on our platform so you can see the difference.
1Send your list of school websites
2We scan every one of them
3You get the report and a sample rebuild
Request the free auditOn the next page, paste your list of school websites into the details box — we'll take it from there.
Prefer a briefing first?
Thirty minutes with your comms, technology and procurement people in the room. We'll run our accessibility checks against your live school sites while you watch, and answer the data-privacy questions on the call.
Arrange a briefingMid-RFP?
Send it over. We respond to district procurement regularly — and we'll tell you honestly if we're not a fit.
Buying for one school?
The single-school platform has its own page, including a free 48-hour site rebuild.
See the school platform