Skip to content
Certrevo
Platform

Seven layers. One student record.

A student appears in your catalog once. That record carries their application, their decision, their seat in a cohort, their invoice, the work they hand in, and their credential — so nothing is retyped and nobody falls between tools.

01Site & catalog

The front of your business, on your own domain

A course platform will give you a site. What it will not give you is a catalog where a one-click workshop and a nine-month fellowship sit side by side, each showing a student what is being asked of them — because it has no idea what an application is. This is the website and the catalog together, on your domain, and a visitor never sees whose software it is.

Open this layer
CatalogSample interface
The public program catalog. Each program carries its own enrollment format — one-click, application, live cohort or bootcamp — so a student sees what is being asked of them before they commit. Illustrative, with sample data.
02Enrollment

Apply and be reviewed, or pay and be in

This is set per program, not per platform. If your program has a decision behind it you need an admissions office: states, reviewers, and a message that goes out every time something changes. If it does not, you need a button. Certrevo has both.

Open this layer
AdmissionsSample interface
The review pipeline. Every applicant sits in a state you can filter and act on, reviewers leave notes the applicant never sees, and a bulk decision still sends each person their own email. Illustrative, with sample data.
03Programs

Five formats, one catalog, no rebuilds

One-click, application-based, recorded, live cohort, and long-running bootcamps and fellowships. All five are programs in the same catalog, and the format is a setting rather than a different product — so a recorded course with no calendar and a nine-month fellowship with a review committee are built the same way and run side by side.

Open this layer
CalendarSample interface
A cohort's schedule down to the individual session, each with its own host, join link, materials and recording. Live, upcoming and finished states keep themselves current, and the whole grid is scaffolded in one action. Illustrative, with sample data.
04Tuition

Invoice on acceptance. Then actually collect.

The gap between an acceptance email and money in the bank is where education businesses quietly lose most of their revenue. Certrevo treats that gap as a queue with an owner.

Open this layer
What you're owedSample interface
A built-in audience for everyone you accepted who has not paid yet, kept live rather than rebuilt as a filter every Monday. The recipient count is shown before a reminder goes anywhere. Illustrative, with sample data.
05Coursework

The teaching, and whether it is landing

Getting someone enrolled is the easy half. The other half is whether they are still with you in week six — which you cannot know if the lessons live in one tool, the assignments in another, and the register in a spreadsheet.

Open this layer
CourseworkSample interface
What a student works through inside a program: recorded and live lessons, assignments to submit, and quizzes to pass. Their progress is tracked per item, so you can see who is keeping up before the cohort ends. Illustrative, with sample data.
06Certificates

Credentials an employer can actually check

A certificate is worth exactly what someone can confirm about it. A PDF is worth nothing — anyone can retype one. Every credential Certrevo issues has an address of its own.

Open this layer
VerificationSample interface
The public page anyone can open to check a credential. The render is frozen at the moment of issue, so editing next year's template cannot change a certificate already in someone's hands — and a revocation fails verification everywhere, immediately. Illustrative, with sample data.
07Team

Hand it to your team without handing over the keys

You are not the person who will spend all day in this. Coordinators, instructors and assistants are. The console assumes that from the start.

Open this layer
TeamSample interface
Five roles, so an instructor can publish without the owner unblocking every change — and without seeing the payment ledger. Illustrative, with sample data.

The layers are the point, not the count.

Any one of these seven exists as a separate product you could go and buy. What you cannot buy separately is that confirming a payment is the same event that opens the coursework, and that finishing the coursework is what a certificate gets issued against. Nobody is retyped between the two. That is the whole argument.

See it with your own program

Bring one real program. Leave with a clear plan.

In thirty minutes, we will map how your current program moves from its public page to enrollment, tuition, teaching, and the final certificate—and tell you plainly where Certrevo fits.

Book a walkthroughSee the live product