Skip to content
Learning PlatformsD-07Live in production

Solara

A coding school for every age — live small-group classes, self-paced lessons and certificates

Timeline
2026 — present
Availability
solara.zyntlow.com
Repositories
1
Role
Product design, architecture and full-stack implementation
Summary
A coding school from little learners at three to adults changing career. Live small-group classes, self-paced lessons and quizzes, XP, streaks and badges, and certificates at the end. Families buy directly; schools either share a referral code or run their own branded school on top of it.
3–5
Youngest learners
through kids, tweens, teens and adults
14
API modules
catalog, learn, live, family, partner, studio, commerce, safety
65
Database tables
one PostgreSQL schema
84k
Lines of TypeScript
measured across apps and shared packages
25%
Partner commission
for a school running its own branded campus; 15% for a referral

What we built

Solara, in use

Sample data, real screens. The product itself is atsolara.zyntlow.com.

A child opens Solara to a streak to keep, a level to reach and a week of days lit up. One lesson is enough to keep the streak going.

What it is

Solara is a coding school, live at solara.zyntlow.com. A child of eight joins a live class that is on right now. A fifteen-year-old works through Python for Teens alongside BECE and WASSCE ICT. An adult changing career starts at Coding from Zero and finishes with a certificate. Each one has their own way in, and the product does not pretend they are the same person.

The name is from the Latin sol — the sun.

The hard parts

Five audiences, one product. A three-year-old cannot read a dashboard and an adult will not tolerate a cartoon. Age bands are a first-class concept in the shared package — they decide the way in, the pacing, the language and what a parent is allowed to see. Children sign in with their name and a PIN, never an email address.

Families, not users. A parent holds the profiles: switch into a child’s account, set the PIN and the controls, read the reports, sit in on a class. The child’s own view stays their own. Getting that wrong in either direction — a parent who cannot see, or a child with no privacy at all — makes the product unusable for one of them.

Two ways for a school to join. A school can share a referral code and earn 15% of every paid enrolment, with Solara’s certificate at the end. Or it can run Northridge Online at its own path, under its own brand, with its students on the roll in cohorts, earn 25%, and have its name on the certificate next to Solara’s. Both models are modelled properly — roll, cohorts, brand, commission and payouts — rather than being a discount code bolted on.

Code that runs in the browser. Blocks for the youngest, then JavaScript and Python in web workers, a turtle stage, and a page builder for first web pages. Nothing to install, and nothing a school laptop will block.

Architecture

The same stack and house style as Digital Campus — the same shell, design system, live room and payment flow, recoloured — which is why a second full platform could ship in the same year as the first.

  • API — Fastify with Drizzle over PostgreSQL 16; src/core for database, auth context, realtime, live rooms, payments and the learning engine, and 14 modules over the top.
  • App — React and Vite, src/ui as the design system, src/features/* for catalogue, learn, live, family, partner, studio, commerce and safety.
  • Live — LiveKit when it is configured; without it, classes run in practice mode with presence, chat, hands and reactions, so the product is never undemonstrable.
  • Deploy — Docker Compose: app, PostgreSQL, Caddy for HTTPS, nightly backups of database and files, with restore drills and health checks documented.
  • Checks — typecheck, tests, Playwright journeys for the main flows, and a guard that fails the build on a gradient or an edited committed migration.
Next product
Strongroom

A password vault, client tracker and team notebook for an agency — the server cannot read the vault