Vibe coding for CIOs in education.
A university or district CIO runs the student information system, the learning platform and the identity provider, and answers to the FERPA officer and the accessibility office. Faculty and registrar staff export student records to build their own tools every week. Term start is when all of them get used at once.
What is true about software in education before you write a prompt.
Schools, universities, training companies and edtech businesses all have the same shape of problem: a learning platform that does most things and a long tail of tools it does not. Executives are building the tail: an enrolment workflow, a parent portal, an assessment tool, a course marketplace. Most of them hold data about students, and some of those students are children.
Student data has its own laws
FERPA in the United States, GDPR in Europe, and rules about children's data almost everywhere. A tool that stores a student's name, grades or attendance is regulated, and a tool used by under-13s has additional consent requirements.
Parents, students and staff see different things
Role-based access is not optional. A parent must see only their child. A student must not see another's grades. The AI will build a single login unless told otherwise.
Accessibility is required
Education tools are often legally required to be accessible. A page built fast with no attention to screen readers or keyboard navigation can be non-compliant on day one.
Term start is your launch day
Enrolment tools and portals get their year's traffic in one week. Hosting and caching have to be ready for it, and a failure that week costs a term's trust.
What a CIO in education gets back first.
01The department that invents its own login
A template that signs users in through the campus single sign-on and reads staff, student or parent from the directory. Departments stop building authentication, and a parent cannot be shown another family's child.
02The CSV of grades exported to build a dashboard
One read-only service that answers approved questions from Banner, PowerSchool or Ellucian and returns only the fields a tool is cleared for. The exports stop, and you can see which tool reads what.
03The accessibility complaint that arrives after launch
Keyboard navigation, labels and contrast already correct in the template, with an automated check in the pipeline. A faculty-built page is still the institution's page, and remediating one after the fact costs far more than the check.
Four more hold for CIOs in any industry. They are on the CIO page.
A registrar's export becomes a FERPA incident
A registrar's office builds a waitlist tool from a CSV export of the student system, hosted on a personal account, holding names, IDs and grades for every enrolled student. It goes live in the first week of term, falls over under the load, and a student finds another student's record in the error page. FERPA requires the institution to respond, the state student privacy law may require notification, and the tool students needed that week is gone.
The pattern underneath is the one every CIO hits: every department app is connected to a real system with a real key, hosted on someone's personal account, with no offboarding. When they leave, the app stays, and so does the access.
What a safe build in education usually runs on.
Builds run on a standard web stack with Postgres, single sign-on from the institution's identity provider or a properly scoped login for parents and students, integrations with the learning platform and the student information system through read-only keys, and accessibility checked before launch.
What changes for a CIO in education.
A CTO in your corner helps you build the rules as software: a template with single sign-on, secret storage, logging and hosting already correct, so the departmental builder starts safe. And a CTO in chat for the moments when someone's tool touches something it should not. You keep the speed the business has discovered. You get the control back.
What CIOs in education ask.
A CTO who has read education apps before yours.
Thirty minutes, free, no card. What you built, what is going on with it, whether we can help.
In your corner.