Zeus Software/Work/Slotify · UniPD
Case studyUniversity of Padua · 2025

Slotify.
One platform,
every resource.

From the meeting room to the electron microscope — one booking system for the whole university.

Client
University of Padua
Sector
Higher Education
Year
2025 · in production
Slotify — booking wizard: resource, fund, time slot, confirmation
A booking in 30 seconds. It used to mean an email to the manager, an Excel sheet, an internal ticket.University of Padua · May 2026
01

One interface
for wildly different resources.

Slotify centralizes booking for the University of Padua's shared resources: rooms, instruments, labs, equipment. Pricing tiered by user category, charges billed to research funds and projects, reporting back to central administration.

02

Where we
started.

Three departments, three different systems. Excel for rooms, email for labs, paper sheets for instruments. Rates applied from memory, reporting reconstructed at year-end. One shared service, a fragmented process.

i.

The challenge

Unify booking for hundreds of heterogeneous resources — meeting rooms, electron microscopes, cleanrooms — without forcing one process onto departments with different rules. Rates for five user categories. Charges billed to research funds. Full audit trail for central administration.

ii.

Our approach

One platform, configurable per department. Identity derived from the university's SAML, rates calculated at login, approval rules chosen by the department manager. Demos every Friday, a first version in production within six weeks, continuous refinement with real users.

iii.

The result

A single source of truth for university-wide bookings. Three legacy systems replaced, automatic reporting to administration, a complete audit trail. The same system serves the meeting room and the electron microscope alike — the same experience for the person booking, different rules under the hood.

03

Five profiles,
one interface.

Context-aware permissions via CASL: each role sees only what it needs, and can only do what the department has authorized.

i.

Researchers
& faculty

Book instruments and labs, charge to research projects, download reports.

ii.

Department
managers

Configure resources, pricing rules, approval thresholds, recurring calendars.

iii.

External
users

Companies, spin-offs, partner institutions. Dedicated rates and mandatory approval.

iv.

Central
administrators

Cross-departmental governance, audits, university-wide policy configuration, consolidated reporting.

04

What it does,
in practice.

Eight capabilities that share the same grammar — from meeting room to electron microscope, the rules underneath change, the experience doesn't.

01

Atomic
& capacity-based

Exclusive slots or concurrent seats. Same model, two uses.

02

Availability
via RRule

iCalendar standard. Exceptions and maintenance windows managed with the same syntax.

03

Public
calendar, QR

Every resource has its own shareable calendar. A QR code to post on the door.

04

Multi-level
approvals

Configurable workflows: none, single, chain. Set by the department.

05

Pricing
per metric

Rates per hour, day, unit. Set on the resource, calculated at booking time.

06

Funds and
projects

Charges tracked to funds, budget caps, authorizations and named principal investigators.

07

Automatic
reminders

Confirmation, reminders, follow-up. Transactional emails in Italian and English.

08

Reporting
and transactions

Full history. Exports for administration, utilization rates for facility managers.

05

Three tiers,
one source of truth.

The user category is derived from SAML identity at login. No forms to fill in, no ambiguity about which rate applies.

i.

Internal UniPD

1.0×

Faculty and staff, researchers, PhD students, students. Reference rate.

ii.

Partner institutions

1.5×

Partner universities, public bodies, spin-offs. Multiplier applied under an active agreement.

iii.

External users

3.0×

Companies, professionals, private individuals. Mandatory approval.

06

University identity,
context-aware permissions.

Three layers sharing the same logic: identity decides who you are, CASL decides what you can do, JWT signs every request.

i.

SSO
SAML 2.0

UniPD federation. No local accounts, identity lifecycle governed by the university.

ii.

Signed JWT
RSA-PSS

API tokens with asymmetric keys and probabilistic padding. Rotation is managed.

iii.

Permissions
via CASL

Five context-aware roles. Permissions evaluated at the level of a single object.

07

Tech stack.

Full-stack TypeScript, infrastructure-as-code deploys. Tools we choose, not collect.

FrontendNext.js 16
UIReact 19
LanguageTypeScript
StateZustand
i18nLingui
DesignBootstrap Italia
ORMPrisma 7
DatabasePostgreSQL 16
AuthZCASL
AuthNSAML 2.0
CloudAWS ECS
IaCTerraform
08 Slotify centralizes booking for university resources: from the meeting room to the electron microscope.
Are you a university or public institution?

Still booking
via email and Excel?

We build multi-tenant booking systems for universities and public institutions, with SAML federation, tiered pricing and automatic reporting. Send us a couple of lines — we reply within 48 hours with an initial technical response and a sense of next steps.