Apex Hub is a full operations portal for a music academy — admin, teacher, parent and store roles, scheduling and payroll, achievement badges, and SPEI/card payments, in one place. It was HAXOR's first deployment, and we run it every day, so the product is shaped by real operations, not a roadmap.
Everyone the academy touches gets the view they need — and nothing they don't. Admin, teachers, parents and the store, on the same system.
Class calendars, teacher assignments, and a roster per session that takes attendance in a tap. Reschedules and make-up lessons stop living in a group chat and start living in the system.
Tuition, enrolment and the summer program, collected by SPEI transfer or card, with receipts issued automatically and a clear per-family balance. Parents pay the way they already pay for everything else.
Teacher pay tied to the sessions actually taught, and a store role for instrument sales, rentals and method books — the two ledgers most academies keep on paper, folded into the same system as everything else.
Achievement badges mark real progress, and parents get a clean view of their child's schedule, attendance, payments and milestones — so the academy communicates through the product instead of a hundred messages a week.
We don't demo Apex Hub from a slide. We run our own academy on it, every day.
— Apex Hub, a HAXOR product
Teaching, collecting, paying and selling — most schools run each on a different tool, or none at all.
Admin, teacher, parent and store are genuinely different jobs. Apex Hub gives each its own surface with row-level security underneath, so a parent never sees payroll and a teacher never sees another family's balance.
Tuition is recurring, families fall behind, and chasing it by hand burns the front desk. Payments, receipts and per-family balances live in the system, so who owes what is a screen, not a spreadsheet.
Payroll ties back to the sessions actually delivered and attendance actually taken. The pay run reconciles against the calendar instead of a manual tally at the end of the month.
Achievement badges and a parent view make progress visible. When families can see the milestones their child is hitting, they stay — retention is a product feature, not a marketing campaign.
We scope it against how your academy really runs, pilot it on live classes, and hand over a system your staff owns.
Your programs, your tuition model, how you pay teachers, and where the front desk loses time. If Apex Hub isn't the right fit, we say so on the first call.
We load students, classes and teachers, wire up SPEI and card payments, and run real scheduling and collection live, with the lead engineer on hand.
Full rollout across roles, an operating runbook, and priority support from the people who build and run it daily. A written, priced scope follows discovery — no surprises.
Engineered, owned and supported by HAXOR — and the one system we run our own operation on.
Apex Hub was HAXOR's first deployment. We built it for a working music academy and then kept running it, which means every feature earned its place by surviving contact with a real front desk, real parents and a real pay run — not a backlog vote.
It rides the same spine as every HAXOR system: a typed backend, Postgres with row-level security, real payment rails, and an automation layer that does the boring work. Because we dogfood it daily, it's the clearest case study we have of what HAXOR ships — and the same engine is why more than one system shipped from one operator.
Book a 30-minute walkthrough with HAXOR. We'll show you the exact workflows we run every day — and tell you honestly if it isn't the right fit for your academy.