Skip to content

Run your hostel
from the bed up

Housekeeping, maintenance, rota, clock-in and guest requests for every bed and every member of staff, built inside a working hostel.

In production. A working hostel runs on it every day.

Three buildings and 54 rooms on one map at 09:58: every few seconds a housekeeper finishes a room, the tile turns green, the counts update and the phone beside the map shows who marked which bed ready.

antie
Updated 09:58
North House0 percent ready%
18 rooms7 ready5 dirty
Ground floor6 rooms
First floor6 rooms
Second floor6 rooms
Mill House0 percent ready%
18 rooms7 ready6 dirty
Ground floor6 rooms
First floor6 rooms
Second floor6 rooms
Annex0 percent ready%
18 rooms10 ready6 dirty
Ground floor9 rooms
First floor9 rooms
Room 204
Mill House · 6 beds
  • ABed AReady
  • BBed BReady
  • CBed CDirty
  • DBed DStay over
  • EBed EReady
  • FBed FReady
ASession runningAna · bedsTimer 07:12

Where your hostel actually lives today

Group chats, a rota file and paper notes. They work until someone asks who cleaned bed 4, and that is where things get lost.

A group chat asks who cleaned bed 4 and nobody is sure, the rota is a spreadsheet called v3 final FINAL, and a paper note reports a dripping tap; under them one Antie line reads 09:58, Ana marked bed 204-C ready, staff app.

Keep chatting. Keep the record somewhere it can be found.

Replaces the group chats, the rota file, the paper logs and the lost property cupboard. Not your PMS.

One app, whole staff

Housekeepers, reception, maintenance, supervisors and management open the same app. Each role sees its part, and guests get a page of their own.

Cleaners see a short list of rooms, not a dashboard. New staff practise in a training copy first.

  • 1 app
  • phone, desk and lobby TV
  • a guest page per bed
  • a training copy for new staff

Six staff roles and the guest page open the same app. The phone shows the first screen each one sees, from the housekeeping room list to the guest page with Wi-Fi, late checkout, luggage storage and SOS; the role buttons switch between them.

Rooms
North House · Ground floor
North House11 / 18 ready
  • 1014 bedsAll doneReady
  • 1026 beds2 leftAna
  • 1038 beds5 leftDirty
  • 1046 beds4 leftDirty
  • 1054 bedsAll doneCheck
  • 10610 bedsAll doneReady

See every bed as it changes

A room is red while its beds are dirty, amber while a housekeeper is in it, green once the last bed is marked ready. The map changes for everyone at once.

Quayside HostelDay clock 06:00

By 11:30 most rooms in the three buildings are green and the map shows which housekeeper is on each room still in progress.

LMon shift
North House6 of 18 rooms ready · 120 beds
33%
Second floor
First floor
Ground floor
Mill House5 of 18 rooms ready · 120 beds
28%
Second floor
First floor
Ground floor
Annex5 of 18 rooms ready · 120 beds
28%
First floor
Ground floor

Red: dirty beds. Amber: someone in the room. Green: all ready. Hover a room for its beds, click a pill to filter.

After a second housekeeper joins at 12:10 the forecast end time for North House drops from 14:31 to 14:07, ahead of the 14:30 deadline.

Day plan
North HouseDeadline 14:30
EndsEnds 14:39+9 min
  • AR
  • TK
  • PN
Beds 2 · Cleaning 1

Plan from the morning import and your own past days.

A plan that updates as rooms get done

The morning import gives every room a time and every building an end time. As rooms get done, what is left is re-scheduled from now.

Traceability

Open any bed. See who did what

Every bed keeps its own activity log, from the morning import to check-in. Open a bed and read the day back, minute by minute.

Six events on bed 204-C in one day, each with a time, a person and a source: the morning import set it dirty, Ana started cleaning at 09:41 and marked it ready at 09:58, Priya passed the cleaning at 10:05, Luca gave final approval at 10:20 and reception checked a guest in at 15:10.

Bed 204-CMill Housetoday
  • who · what · whenEvery action: who, what, when
  • 204-CBed history kept per bed
  • supervisorSupervisors see the full trail

Maintenance and lost property

Nothing reported gets lost in a chat

A dripping tap gets a ticket with a number, a priority and an owner. A charger left in a bed gets a photo, a bag and a printed QR label.

Tomasz K. reports a dripping tap in room 118 with a photo at 08:12. It becomes ticket #M-118, priority Normal. Luca M. takes it at 09:05 and the status goes to In progress. Luca M. comments that it is fixed and mentions Tomasz, who gets a push. The ticket closes at 11:20.

New report08:12#M-118Normal08:12

Tap dripping in the bathroom

Room 118 · North HouseTomasz K.Luca M.
  1. 08:12Tomasz K. reported it from room 118, photo attached
  2. 09:05Luca M. took the ticket
  3. 09:05Status set to In progress
  4. Luca M.11:18Fixed the washer. @Tomasz can you check it tomorrow morning?Push sent to Tomasz K.
Closed 11:20by Luca M.
08:12Tomasz K. reports it, with a photo

Item #LF-0427, a black phone charger found in room 204 bed C, gets a printed label with a QR code, its reference, the date and bag B-17.

#LF-0427Stored

Black phone charger

Room 204 bed C · found 10:02 by Ana

Bag B-17Expires in 90 days
LF-0427Black phone charger12 Oct 2026 · 10:02Room 204 bed CBag B-17antie
  • 01Ticket numbers are fixed at creation. #M-118 stays #M-118 in every list and search.
  • 02Mention a colleague and they get the push, even in a muted group. Follow any ticket.
  • 03Items are sealed into numbered bags. The seal number sits next to the item id.
  • 04After 90 days an item expires and moves to a supervisor-only disposal queue.
  • 05Labels print on a Zebra thermal printer, 100 by 50 mm, with a QR to the item.

Plan the week without telling anyone

Build next week in a draft while the team still sees the published schedule. The Helper flags rest and coverage gaps. Publish when you are ready.

A manager fixes a rest warning in the draft schedule, publishes it, and five minutes later only Tomasz receives a push about his Wednesday shift.

Schedule published. Staff notified in 5 minutes

The schedule and the clock, side by side

  • Clock in with an NFC tap on the staff phone
  • Forgotten sessions close automatically and wait for approval
  • Fix requests come from the staff, approvals from the manager
StaffPlanned, clockedDiff
Ana R.Housekeeping08:00 to 16:0007:56 to 16:04+8 min
Tomasz K.Housekeeping08:00 to 16:0008:11 to 16:02-9 min
Priya N.Housekeeping08:00 to 16:0007:58 to 15:40, 20 min early, flagged-18 min
Luca M.Supervisor07:30 to 15:3007:25 to 15:35+10 min

Red: more than 15 min from the schedule

Chat, news and SOS alerts for the team

Chat with voice notes, news with read confirmation, and an SOS alert that reaches every staff phone and fills the reception screens until someone answers.

The Housekeeping group is muted. A message from Luca mentioning Priya arrives anyway, unmutes the phone and shows a banner that reads Mention from Luca.

Housekeeping6 members · muted
Today
Tomasz K.
0:09
10:34
Ana R.The linen trolley is on the first floor, by the lift.10:36
Thanks, taking two bags up now.10:37
ChatVoice notes transcribed, messages translated, mentions through the mute.

The post Fire drill Thursday 10:00 shows 23 of 31 read. Pressing Acknowledge adds you to the readers and the count becomes 24 of 31.

Company NewsStreams · 31 members
Maya O.Manager · Tue 09:12

Fire drill Thursday 10:00

Meet in the courtyard. Supervisors count their floors and report to reception. Takes 15 minutes.

23 of 31 read read8 to confirm
StreamsCompany news asks for a read confirmation. The author sees who has not confirmed.

An SOS from room 310 in the Annex covers the whole phone. Pressing On my way collapses it to a chip that reads Jonas is on his way with the time since he answered. Resolving the alert needs a note.

RoomsAnnex
Guest SOSRoom 310 · AnnexPlease come to meBed B · location from the QR card
SOSTakes over every staff phone until someone answers. Resolving requires a note.
  • A mention in a muted group still reaches the person named.
  • Company news asks for read confirmation and lists who has not confirmed.
  • SOS alerts every staff phone and fills every reception screen until someone answers, then closes with a note.

The guest scans. Reception sees it

A QR card on every bed gives guests the Wi-Fi, a help button and a late checkout paid by card. Each request lands at reception and the guest sees its status.

Scanning the card of room 204 bed C opens Guest Connect on the phone with the Wi-Fi and four buttons. Late checkout costs €5 until 12:00 or €10 until 14:00. Paying shows reception notified, and the tile for room 204 on reception's map gets an LC pill. Beside the card, reception's early check-in request for room 310 shows a housekeeper accepted it.

Printed card by the bed. Hover, focus or press to scan.
Reception · Early check-inRoom 310 · bed asked for 11:40
  • 11:02Jonas F. sent an urgent bed request
  • 11:04Ana R. accepted on her phone
  • Escalates if nobody picks it up. Posted to the reservation.
16:05Point the camera at the card
Reception · Quayside Hostel · Mill House
Reception sees it on the map
  • A QR card in every bed and every restroom, printed from the system.
  • Late checkout is bought from the guest’s phone or sold at the desk. The bed is held until the chosen time.
  • Early check-in goes out from reception as an urgent bed request. A housekeeper accepts it on their phone.
  • Nothing a guest asks for gets lost. They see the status of their request and the hostel looks attentive.
  • SOS from the guest phone reaches staff with the bed location attached.
  • Luggage storage is requested from the phone and paid when the guest collects the bags.

Seen enough to want it on your own hostel?

Book a demo

In production. A working hostel runs on it every day.

Works beside your PMS

Keep your PMS. Add what it does not do.

Antie imports beds and arrivals from your PMS each morning and posts guest sales back to the reservation. Nobody types the same thing twice.

Beds and arrivals come in from the PMS with the morning import and the departure rooms turn red on the map; a €10 late checkout sold in Antie is posted back as a line on the reservation folio.

One morning
Morning import of beds and arrivals. The hour is set per hostel.
If the import did not land, a retry runs on its own.
A no-show arrives by webhook. The bed moves on the map on its own.
Housekeeping status goes back to the PMS after the supervisor gives the OK.
example times
No double entry. The map and the folio agree.
  • Many PMSs have nothing for late checkout or early check-in. Antie sells one, dispatches the other, posts both.
  • With an API connection, no-shows and date changes arrive by webhook. The bed moves on the map on its own.
  • Housekeeping status goes back to the PMS once the supervisor gives the OK.
  • The morning import runs at the hour your hostel sets. If it does not land, a retry runs on its own.

If your PMS offers an API, we connect to it. Ask in the demo.

Security and permissions

Each staff account, its own switches

Every account has its own set of permission switches. Flip one and it takes effect on the next request, with the change on record.

  • About 60 permission switches per account, re-checked on every request. No cache.
  • Sessions expire after 12 hours.
  • Deletions are soft. The record stays.
  • Every change is logged with who did it and when.
  • Postgres database, backed up every day, behind Cloudflare.
  • A training copy for new staff that never touches real data.

Flipping a permission switch greys out or restores the matching section in the app rail of that role at once, and the change is written to the audit log with who did it and when.

Users · permissions6 of about 60 switches
RoleBeds workflowMaintenanceLost & foundScheduleReportsPayments

Reception sees 2 of 6 sections. Re-checked on every request, no cache, no logout needed.

Audit logActionLog · last 4
  1. Flip a switch. Each change is written here with who and when.
Access changes take effect now, and the change itself is on record.

Book a demo

See it on your own hostel

The live product with your buildings and your numbers, not slides. Shown by the person who built it.

I built Antie inside the hostel where I work. I started in housekeeping and moved up to management, so I know what each role needs from the app, and I built it to fix the problems each of them actually has.

Your guests are your customers. Nothing a guest asks for gets lost, they can see where their request stands, and the hostel looks attentive.

Send the form and I will answer your email myself.

Facilities manager, and the person who built Antie

Book a demo for the details.

I'll reply within one business day with times that work.

I only use your details to reply about the demo.

In production. A working hostel runs on it every day.

Antie works beside the PMS you already use. If it offers an API, we connect to it.