Skip to content
CampusesOS

Early access open for pilot universities

Get every campus update to the right students, and know it arrived.

CampusesOS replaces scattered group chats and notice boards with one platform: personal timetables, targeted notices with acknowledgements, emergency alerts, live shuttle and facility status, and an AI assistant that answers from official university information.

Request a demo Explore the product

Built for registry, student affairs, works and transport, and ICT teams.

Mon 13 Oct

Good morning, Ada

300L · CSC
Registry · Requires acknowledgement

CSC 301 exam moved to Main Auditorium

Thu 16 Oct · 10:00 · was LT2

Route A · Science Labs

3 min

Hall B power

On · Generator

Next class

CSC 305 · Operating Systems

10:00

LT3, Faculty Ring

  • 01

    One student app

    Timetable, notices, shuttles, cafeteria, power status, map and events in a single place instead of WhatsApp groups and notice boards.

  • 02

    Targeted notices

    Send to a faculty, hall, level or course and see who has opened and acknowledged it.

  • 03

    Live facility status

    Shuttle positions, cafeteria load and power availability published from sensors or staff updates.

  • 04

    Grounded AI assistant

    Answers student questions only from official notices, handbooks and schedules, with the source attached.

The problem

Universities run on information that rarely reaches the people it is meant for.

Registry, student affairs, works, transport and the student union each publish through their own channels. Students are left stitching together a picture of their week, and staff have no evidence that anything was received.

  1. 01

    Information is scattered

    A typical student checks a faculty WhatsApp group, a hall notice board, the portal, a departmental Telegram channel and a lecturer's email to learn one timetable change.

  2. 02

    Nobody knows who received what

    When the registry moves an exam venue, there is no record of which students saw it. The cost shows up as missed papers, re-sits and appeals.

  3. 03

    Facility questions flood staff

    Is the shuttle running? Is there light in Hall C? How long is the cafeteria queue? Porters, transport officers and student affairs answer the same questions all day.

  4. 04

    It does not scale with enrolment

    Each new intake adds hundreds of group chats and inboxes. Manual relay through class reps breaks down exactly when it matters: emergencies, exam weeks and resumption.

How CampusesOS changes the workflow

Same offices, same information, one delivery layer.

  • Notice posted to 40 group chats by class reps

    One notice targeted to the exact faculty, level, hall or course

  • No way to tell who saw an exam venue change

    Open and acknowledgement record for every critical notice

  • Porters field calls about power and water all day

    Status published once, pushed to the residents who subscribed

  • Students wait at stops with no idea when a shuttle comes

    Live position and arrival estimate per route

  • The same registration questions every semester

    Assistant answers from the official notice and cites it

Core features

Seven modules, one data model for the whole campus.

Each module works on its own, and they share the same students, buildings, courses and roles. A timetable change can trigger a notice, the notice links to the map, and the assistant can answer questions about it.

Mon

CSC 301LT2

Tue

MTH 307LT1

Wed

CSC 305LT3

Thu

CSC 301 ExamMain Aud.
GST 301LT3

Fri

CSC 311 LabLab E2

Clash: GST 301 overlaps CSC 301 exam for 46 students

Smart Timetable

Import course and exam schedules from the registry's spreadsheet or student information system. CampusesOS builds a personal timetable for every student, flags venue clashes before publishing, and pushes changes only to the students affected.

Fewer missed lectures and exam-venue mix-ups after a schedule change.

See it in the workspace

Audience

Faculty of Science300 levelHall C
Water supply to Hall C will be interrupted overnight for pipe repairs…
742 recipients Send

Targeted Notices & Emergency Alerts

Compose a notice once, target it by faculty, department, level, hall or course, and require acknowledgement for critical items. Emergency alerts bypass quiet hours and go out by push, SMS and email.

A verifiable record of who received and acknowledged each notice.

See it in the workspace

When does course registration close?

Friday 17 October at 23:59. Late registration needs the Dean's approval and a penalty fee. Registry notice N-2037

When do we get hall allocation?

No official answer yet · sent to Student Affairs

Campus Assistant

Students ask questions in plain language: "When does course registration close?" The assistant answers only from published notices, handbooks and timetables, cites the source, and hands off to a staff queue when it has no official answer.

Routine questions are answered instantly; staff see the gaps in official information.

See it in the workspace

Route A · SH-04

  1. Main Gate
  2. Faculty Ring
  3. Science Labs3 min
  4. Library
  5. Senate

Shuttle Tracking

GPS units or a driver app report shuttle positions. Students see each route, the next stop and an estimated arrival; transport officers see headway gaps and overcrowded runs.

Shorter waits at stops and evidence for adjusting routes and frequencies.

See it in the workspace
  • Hall AGrid
  • Hall BGenerator
  • Hall COutage 07:48
  • EngineeringMaint. tomorrow
Central Cafeteria
14m

Facility Status: Power & Cafeterias

Publish power availability for halls, lecture theatres and labs, and cafeteria occupancy, from metering devices or a one-tap staff update. Status changes reach subscribed students automatically.

Fewer wasted trips and fewer calls to porters and works department.

See it in the workspace
Main Auditorium

Campus Map & Directory

Searchable map of lecture halls, hostels, clinics, banks, libraries and offices, linked from every timetable entry and notice so students can find the venue they were just sent to.

New students find their way in the first week without asking around.

See it in the workspace
  • Engineering Mathematics, 7th ed. Clear
  • Hostel bed space for transfer Hall policy
  • Laptop repair service Clear

Moderated Marketplace & Events

Students and approved campus vendors list textbooks, gadgets, services and events. Listings pass through a moderation queue with automated checks for prohibited items before going live.

Campus trade and events move off unmoderated chats into a space the university can oversee.

See it in the workspace

How it works

From the registry spreadsheet to a student's lock screen.

CampusesOS sits between the offices that own campus information and the students who need it. Onboarding starts with the data a university already has.

  1. Step 1

    Connect campus data

    Upload buildings, routes, halls and course lists, import timetables, and connect university sign-in. Shuttle GPS and power meters connect where available.

  2. Step 2

    Validate and structure

    CampusesOS checks imports for venue clashes, missing rooms and duplicate courses, and maps every student to their faculty, level, hall and courses.

  3. Step 3

    Apply intelligence

    Official content is indexed for the assistant. Ridership and occupancy history feed arrival and wait-time estimates.

  4. Step 4

    Publish to students

    Personal timetables, targeted notices and live status reach students on web and mobile, with push, SMS and email for what is urgent.

  5. Step 5

    Monitor and act

    The operations console shows acknowledgements, unanswered questions, shuttle gaps and outages so each office can respond.

Interactive product tour

The operations console your offices share.

Try it with a fictional university. Approve a notice, remind students who have not acknowledged, report an outage, moderate a listing, or follow an insight to the record behind it.

  • • Overview: delivery, outages, assistant gaps, insights
  • • Notices: search, filter, approve, send, remind
  • • Facilities: power by building, cafeteria load
  • • Shuttles and marketplace moderation
Lakemere UniversityFirst Semester 2026/27 · Week 7
Sample data

2

Notices awaiting action

Drafts and approvals

76%

Acknowledgement rate

Critical & high priority

1

Buildings without power

of 9 monitored

97

Open assistant questions

Routed to staff, 7 days

Assistant questions by topic

Answered from official source · 1,293 No official answer · 97
RegistrationExamsHostelsFeesTransportClinic

Activity

  1. 187 of 214 students acknowledged “CSC 301 exam moved to Main Auditorium”.08:52
  2. SH-07 on Route A is running 6 minutes late. Riders at Main Gate were notified.08:31
  3. Hall C porter reported a power outage. 742 residents subscribed to Hall C status were updated.07:48
  4. Assistant could not answer 11 questions about hall allocation dates. Routed to Student Affairs.07:20
  5. Registry imported 1,284 timetable entries. 3 venue clashes flagged and resolved.Yesterday

Insights

  • Hall allocation is the top unanswered topic

    38 questions this week asked when returning students will see their hall allocation. No published notice covers it. A draft notice (N-2039) is awaiting Student Affairs approval.

  • Route A is under-served from 07:30 to 08:30

    SH-07 has run full on 4 of the last 5 mornings with an average 9-minute gap at Main Gate. Adding one shuttle in this window would bring the estimated gap under 5 minutes.

  • Listing L-587 likely violates hall policy

    Automated checks matched “bed space for transfer” to the hall allocation policy, which prohibits resale of bed spaces.

Lakemere University and all names, figures and events shown are fictional sample data for demonstration.

Who it's for

Bought by the university, used by every office that talks to students.

CampusesOS is licensed per campus. Each office gets a role-scoped workspace; students get one app.

Student Affairs & Hall Administration

Problem
Hall notices, curfews, allocation updates and welfare messages are relayed through hall reps and get lost.
How they use it
Target notices by hall and level, require acknowledgement for allocation and safety notices, and review the assistant's unanswered questions weekly.
Outcome
Proof of delivery and fewer repeated enquiries at the student affairs desk.

Works, Facilities & Transport

Problem
Outages and shuttle delays generate phone calls and complaints with no shared picture of what is happening.
How they use it
Post power status per building, track shuttles by route, and broadcast disruptions to the affected areas only.
Outcome
One status board for staff and students, and ridership data for planning routes.

Registry & Academic Planning

Problem
Timetable and exam venue changes cause clashes and missed papers when they do not reach every affected student.
How they use it
Import schedules, resolve flagged clashes, and push changes to the students on each affected course.
Outcome
Cleaner exam weeks and an audit trail when a change is disputed.

ICT Directorate

Problem
Every office wants its own app or channel, which multiplies logins, vendors and data silos.
How they use it
Run one platform with university sign-in, role-based access and data exports, instead of supporting several tools.
Outcome
Fewer systems to secure and maintain, with a single data model for campus operations.

Technology

How We Use Amazon Web Services

CampusesOS is designed on AWS as an event-driven, serverless platform. In this architecture, shuttle and power devices stream into AWS IoT Core, every notice and status change is processed by AWS Lambda and stored per university in Amazon DynamoDB, and the campus assistant uses Amazon Bedrock to answer only from documents the university has published. Each stage below maps a product capability to the service responsible for it.

  1. 01

    Data Collection

    • AWS IoT Core
    • Amazon API Gateway

    Shuttle GPS units and power meters publish over MQTT; staff apps and registry imports arrive through authenticated APIs.

  2. 02

    Secure Storage

    • Amazon S3
    • Amazon DynamoDB

    Timetable files and notice attachments in S3; live status, notices and acknowledgements in DynamoDB, partitioned per university.

  3. 03

    Processing

    • AWS Lambda
    • Amazon Location Service

    Event-driven functions validate imports, detect clashes, fan out notices and compute route positions and geofences.

  4. 04

    AI Intelligence

    • Amazon Bedrock
    • Amazon SageMaker AI

    Retrieval-grounded answers over official content; forecasting models for shuttle arrivals and cafeteria wait times.

  5. 05

    Application Experience

    • Amazon Cognito
    • Amazon SNS
    • Amazon CloudFront

    University sign-in, push and SMS alerts, and fast delivery of the student app and admin console.

Services and their role

Each university's data is isolated by tenant, access is scoped by role through Amazon Cognito, and the assistant is restricted to retrieval over the university's own published content.

  • AWS IoT Core: Receives location pings from shuttle GPS units and readings from building power meters over MQTT.
  • Amazon API Gateway: Exposes the authenticated REST APIs used by the student app, admin console and registry imports.
  • AWS Lambda: Runs timetable validation, clash detection, notice fan-out and status-change processing as event-driven functions.
  • Amazon DynamoDB: Stores notices, acknowledgements, facility status and shuttle positions with per-university partitioning.
  • Amazon S3: Holds imported timetable files, notice attachments, marketplace images and the documents indexed for the assistant.
  • Amazon Location Service: Provides campus maps, route tracking and geofences that trigger arrival estimates at shuttle stops.
  • Amazon Bedrock: Powers the campus assistant with retrieval over official notices, handbooks and timetables, and drafts notice summaries for staff review.
  • Amazon SageMaker AI: Trains and hosts models that estimate shuttle arrival times and cafeteria wait times from historical patterns.
  • Amazon Cognito: Handles student and staff sign-in, including federation with a university's existing identity provider.
  • Amazon SNS: Delivers push notifications and SMS for targeted notices and emergency alerts.
  • Amazon SES: Sends notice emails, acknowledgement reminders and website enquiry notifications.
  • Amazon CloudFront: Serves the web app, admin console and this website over a global CDN with TLS.
  • Amazon CloudWatch: Collects logs, metrics and alarms for alert delivery, device connectivity and API health.

Business progress & early access

Founded in 2026. Now building with our first universities.

CampusesOS is in its build stage. We are opening a limited number of pilot places for universities that want to replace fragmented student communication and bring facility status into one place.

What a pilot looks like

  1. 01Scoping

    We map the offices, channels and data sources involved, and agree which modules to start with.

  2. 02Single-campus setup

    Buildings, routes, halls and course lists are imported and validated for one campus.

  3. 03Measured review

    Acknowledgement rates, open questions and support load are reviewed with your team.

Request early access or a demo

Tell us about your campus. Fields marked * are required.

Which offices are involved, and what channels do you use today?

We use these details only to respond to your request. See our Privacy Policy.

Pricing

Licensed per campus, quoted on enrolment and modules.

Every plan includes the student app on web, iOS and Android. We quote after a short scoping call so the price reflects your student population and the modules you need.

Starter

A single campus starting with communication

Custom quote

  • Student web and mobile app
  • Targeted notices with read receipts
  • Emergency alerts
  • Smart timetable import
  • Campus map and directory
  • Email onboarding support
Request pricing
Most requested

Growth

Universities adding live operations and AI

Custom quote

  • Everything in Starter
  • Campus assistant grounded in official content
  • Shuttle tracking and arrival estimates
  • Power and cafeteria status
  • Moderated marketplace and events
  • Operations console and exports
Request pricing

Enterprise

Multi-campus institutions and university systems

Custom quote

  • Everything in Growth
  • Multiple campuses under one account
  • Identity provider federation
  • Custom data integrations
  • Role and audit configuration
  • Dedicated onboarding
Contact sales

Team

The Team Behind CampusesOS

CampusesOS was founded in 2026 by Umar Kabir, with Fedrick Luma leading engineering as CTO. Our approach starts from how information actually moves on a campus, through the registry, student affairs, works and ICT offices, and builds the product around those workflows.

If your institution wants to shape the product during the pilot stage, talk to us directly.

Talk to the founders Follow on LinkedIn
  • UK

    Umar Kabir

    Founder

    Founded CampusesOS and leads company direction, product strategy and partnerships with universities.

    LinkedIn
  • FL

    Fedrick Luma

    Chief Technology Officer

    Leads engineering at CampusesOS, including the platform's architecture on Amazon Web Services.

Contact

Talk to CampusesOS.

Questions about the platform, partnerships or press. For pilot enquiries, the early access form above gives us the most useful detail.