For universities & innovation hubs
Coworking infrastructure
for academic communities.
Innovation hubs, business-school maker spaces, research commons. LiteHQ runs the access tiers, the semester rhythm, and the sponsor reporting so program directors can spend the year on programming, not on calendar tetris.
The campus-hub reality
Three structural mismatches between universities and commercial coworking software.
Universities aren’t coworking spaces with a different logo. They are tiered communities operating on academic calendars, with sponsor obligations that commercial tools were never designed for. The same three patterns come up in every hub program.
Students, faculty and sponsors share the same door.
Different tiers, different hours, different agreements, but one floorplan and one card-reader. The current solution is a printed list at reception and a security guard who guesses. The audit trail is whoever’s memory you trust this week.
Semester schedules break every commercial booking tool.
Fall semester, winter break, exam week, summer school. Most coworking platforms assume Monday-to-Friday forever. The hub director ends up running a parallel Google Sheet because the booking tool can’t model ‘closed for graduation week, but open for the sponsor demo’.
Sponsors want a report you can’t produce.
Every corporate sponsor wants to know how many of THEIR cohort used the space, in what room, on what day. The data is split across an Eventbrite, a key-fob log and a Google Form, and the year-end report ends up being three nights of manual reconciliation.
What we do for you
Three capabilities built for the campus calendar.
Each capability lands on a specific pain the commercial coworking tools cannot model, built from the same tiering, scheduling and ledger primitives that run the rest of LiteHQ.
Tier-based access: student, faculty, sponsor
Three default roles, configurable to your program. Each tier gets its own hours, room set and booking limits, driven by membership, so a student stops being a student when their membership ends, without anyone keeping a parallel list.
- Per-tier room access, hours and booking windows
- Membership end dates expire access on graduation or end-of-engagement
- Magic-link logins today; Google Workspace SSO is on the roadmap
Semester scheduling that the registrar will recognise
Term calendars, exam-week blocks, holiday closures and one-off events all coexist on the same schedule. The hub stays open for the sponsor demo on graduation Friday without breaking the ‘closed for graduation’ rule for everyone else.
- Term and exam-week closures via blackout dates, by resource or location
- Override windows for sponsor events without breaking term rules
- Recurring lab and cohort sessions with one-off exceptions
Sponsor reporting on tap
Group each sponsor's cohort as a company, and every booking and check-in ties back to it. The year-end report is one filter and an export, not three nights of reconciliation. Hand it to advancement or hand it to the sponsor directly.
- Cohorts modelled as companies: bookings and usage roll up per sponsor
- Per-cohort utilization from the same ledger that runs billing
- CSV exports your advancement team can attach to a renewal
Working with us
Straight answers for the procurement form.
The honest version: LiteHQ is month-to-month at a flat $99/mo, no annual contract required. Data is hosted on Supabase in AWS Sydney (ap-southeast-2). We don’t hold certifications we don’t have, and we’ll answer any security questionnaire directly rather than around it.
Spin up a pilot hub self-serve, or email us your program’s requirements and we’ll tell you honestly what LiteHQ models well today and what’s still on the roadmap.
Run your hub on one platform.
Bring tiered access, semester scheduling and sponsor reporting under one roof: flat $99/mo, month-to-month, cancel anytime.