About
From academic practice to institutional software
The product began where daily communication gaps were visible. Today we work with IT, student affairs, and programme offices so the same platform meets operational, security, and governance requirements.
Where it started
The Hague University of Applied Sciences, then wider Dutch campuses
Fragmented email, buried LMS links, and unmanaged informal chat groups: that was our daily routine as students.
Today the codebase powers pilots beyond The Hague, but the instinct is unchanged: ship something students open without a training manual, and give staff numbers they can bring to a programme board.
The Hague University of Applied Sciences, where CampusConnext began
Team
The team behind the product
You work directly with the people who implement integrations and support pilots.
Anastasiia Goncharova
Chief Operating Officer
Runs partner conversations, pilot logistics, and the operational documentation that keeps faculties aligned with central IT. First point of contact when you want a scoped rollout plan.
Luca Degenaar
CTO & Backend Developer
Architects the Supabase/Postgres layer, integration middleware for SIS and roster systems, and the guardrails that keep tenant data apart. Informatics graduate from the founding institution.
Elioth H
Lead UI/UX Designer
Owns the design system for both the student app and the staff publishing console: spacing, typography, accessibility checks, and the handoff files engineers actually implement.
Max Mencl
UI/UX Designer & Communication
Shapes outward-facing storytelling and keeps in-app copy consistent with how Dutch students really talk. Also pushes pixels when Elioth needs an extra pair of hands.
Arina Jevsejeva
UI/UX Designer
Focuses on flows for onboarding, notifications, and community safety, with lots of hallway testing with classmates during the UX degree.
Discuss your campus communications requirements
We will say clearly if we are not a fit. If we are, we propose pilot scope after aligned discovery calls.