Instead of StarRez
Stop renting StarRez. Own your student accommodation system.
We build your version around how your residential life team runs, bring your StarRez bookings across and run it for you.
StarRez publishes no price list. One university's public order shows US$75,620 for a single year's subscription after discount, plus US$19,873.70 to set it up.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
A yearly bill sized by beds and modules
StarRez is quoted privately. Public purchase orders show how the bill is built: beds, staff users, portal users and modules, renewed every year.
Priced by the bed
The order we found covers up to 3,781 beds. Add a building and the bill grows with it.
Capped staff and portal users
That order allows 40 staff and 400 residents online at the same time. The caps are part of what you buy.
Modules sold separately
Software directories list StarRez pricing as per feature. Each new need is another line on the quote.
A price that climbs
In the same order, year one is US$75,620 and years two and three each cost more.
Setup on top
Implementation in that order was US$19,873.70 before a single resident moved in.
Your rules, their screens
Your Code duties live in forms the vendor designed. How a check works depends on what its settings allow.
Your own accommodation system
Ask about residents, rooms and the Code in plain words
Welfare
Know who has not been seen
Activity checks, causes for concern and welfare plans sit in one record, with the review date beside each plan.
- check Residents not seen within your check interval
- check High-risk concerns with no welfare plan flagged the same day
- check Plan reviews due, by the staff member who owns them
- check Under-18 residents with no guardian phone on file
Contracts
No signing before the house rules
Offers, contracts and room assignments follow the order the Code sets out.
- check Signing is refused until house rules and complaints information are recorded
- check The refund policy written on every contract
- check A room never booked past its beds
- check No check-in without a signed contract
The building
Notice, repairs and the complaints log
Routine room entries, urgent repairs and complaints are kept as a record the Code asks for.
- check A routine entry with less than 24 hours' notice is refused
- check Heating, damp and security repairs past your target flagged
- check A complaints log residents can read, with names left off
- check An evacuation roll for each building, printed in seconds
Money
Fees and arrears without the portal
Weekly fees raised in one step, payments matched by reference, statements in your brand.
- check Fees raised for every signed stay, never twice
- check Arrears by days overdue, oldest first
- check A drafted arrears letter that offers a plan
- check An accommodation statement for each resident
Make it yours
Design your own StarRez replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from StarRez. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your StarRez data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from fictional demo halls. Ask about the Code, welfare and free rooms, then see the records behind each answer.
Student Accommodation for Claude Code
Connected to your own database
Are we meeting the Pastoral Care Code in our halls right now?
ACTIVITY_CHECK
- Subject
- Jack O'Neill
- Issue
- No recorded check for 9 days
ACTIVITY_CHECK
- Subject
- Priya Raman
- Issue
- No recorded check for 12 days
AT_RISK_NO_PLAN
- Subject
- Priya Raman
- Issue
- High-risk concern raised 2026-10-10 with no open welfare ...
COMPLAINT_OPEN
- Subject
- Kowhai House
- Issue
- Complaint received 2026-09-19 open 26 days: Noise from th...
CONTRACT_TERMS
- Subject
- Hannah Brooks
- Issue
- Contract for Second semester has no refund policy recorded
DISCLOSURE_BEFORE_SIGNING
- Subject
- Sione Fifita
- Issue
- Signed 2026-07-27 without house rules or complaints infor...
PLAN_REVIEW_OVERDUE
- Subject
- Mei Tanaka
- Issue
- Welfare plan review was due 2026-10-11
ROOM_ENTRY_NOTICE
- Subject
- Kowhai House KH-103
- Issue
- Routine entry 2026-10-12 11:22 with 6.0 hours notice
UNDER_18_GUARDIAN
- Subject
- Liam Chen
- Issue
- Under 18 at start of Academic year with no parent or guar...
URGENT_REPAIR
- Subject
- Rata Court RC-01
- Issue
- heating reported 2026-10-10, open 5 days: Wall heater not...
| Rule | Subject | Issue |
|---|---|---|
| ACTIVITY_CHECK | Jack O'Neill | No recorded check for 9 days |
| ACTIVITY_CHECK | Priya Raman | No recorded check for 12 days |
| AT_RISK_NO_PLAN | Priya Raman | High-risk concern raised 2026-10-10 with no open welfare ... |
| COMPLAINT_OPEN | Kowhai House | Complaint received 2026-09-19 open 26 days: Noise from th... |
| CONTRACT_TERMS | Hannah Brooks | Contract for Second semester has no refund policy recorded |
| DISCLOSURE_BEFORE_SIGNING | Sione Fifita | Signed 2026-07-27 without house rules or complaints infor... |
| PLAN_REVIEW_OVERDUE | Mei Tanaka | Welfare plan review was due 2026-10-11 |
| ROOM_ENTRY_NOTICE | Kowhai House KH-103 | Routine entry 2026-10-12 11:22 with 6.0 hours notice |
| UNDER_18_GUARDIAN | Liam Chen | Under 18 at start of Academic year with no parent or guar... |
| URGENT_REPAIR | Rata Court RC-01 | heating reported 2026-10-10, open 5 days: Wall heater not... |
Ask it anything
Ten questions your accommodation system answers
Each works against the records in the free version today. Your version adds your own.
Switching
How to switch from StarRez
In practice, the move involves exporting your records, mapping and checking the import, then running both systems side by side before you stop using StarRez.
- 1
Export your StarRez records
Build a booking report in StarRez and save it as a CSV. That report brings across buildings, rooms, residents and each booking with its dates and weekly fee. Transactions, incident notes and portal history need their own exports. Export what your account allows, usually CSV or Excel, and check with StarRez if you are unsure how to get those records out.
- 2
Preview and load the records
Start with a preview of the booking report before loading it. Check that the report is the one you intended to use and that the preview looks right. Once you are satisfied, load the records into the new system. If you have separate exports for transactions, incident notes or portal history, have those mapped as part of the switch too.
- 3
Review the import results
Review what the preview flags before you rely on the imported records. Check the buildings, rooms, residents, booking dates and weekly fees against StarRez, and follow up on anything that looks missing or incorrect. Pay particular attention to any records or history that came from separate exports, since they need their own mapping rather than coming across in the booking report.
- 4
Run both systems side by side
For a short period, keep StarRez available while you use the new system for current work. Compare the records and make sure new bookings and changes are being captured correctly. Check the transactions, incident notes and portal history you chose to bring across. This gives you a chance to spot gaps and correct them before StarRez is no longer your working system.
- 5
Switch off StarRez
When you have checked the imported records and are confident the new system is ready for current work, stop using StarRez as your working system. Keep the exports you need for your own records, including any history you chose not to bring across. The new system stores its records in a database you own, but it does not have a web front end.
Where the real effort goes
The main work is usually mapping your own fields and rules, then deciding how much history to bring across. Buildings, rooms, residents and bookings come from the booking report, while transactions, incident notes and portal history need separate exports and mapping. If Enterprise DNA installs and runs the system for you, they handle this migration work as part of the switch.
Not ready for a call?
Get your StarRez switch plan by email
We will send you the step-by-step plan for moving your business off StarRez, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your StarRez switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Choose who builds and runs your version
Open source
Do it yourself
Free, MIT licence
- 1 Clone the repo and run npm install
- 2 Run npm run demo and ask Claude Code what needs attention
- 3 Works with Claude Code, Codex, OpenCode or Cursor
- 4 Import a StarRez booking report saved as CSV
Built around your business
We customise it
One setup fee, then a retainer
- check Your halls, room types, fees and house rules
- check Your StarRez bookings and history mapped and checked
- check A resident portal for applications and room choice if you want one
- check A phone screen for resident assistants logging checks
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and operated through Omni by Enterprise DNA
- check Connected to your finance system and student records where agreed
- check Backups, support and changes each term
- check The Code checks kept current as the rules change
Questions
Instead of StarRez, answered
What comes across from StarRez? expand_more
A StarRez booking report saved as a spreadsheet brings buildings, rooms, residents and each booking with its dates and weekly fee. Transactions, incident notes and portal history need their own exports, and we map those for you as part of the switch.
Our residents apply and pick rooms online. What happens to that? expand_more
The free version has no resident portal: staff enter or import what residents send. If online applications matter to you, we build a portal on the same records as part of your version.
Does this make us compliant with the Pastoral Care Code? expand_more
No system can. It checks your records against the accommodation clauses that can be checked from data, such as notice before room entry, welfare plans and the complaints log, and cites the clause for each. You still complete the annual self-review against the whole Code.
Welfare notes are sensitive. Who can see them? expand_more
They sit in a database you own rather than inside a vendor's product. We set up access so only the welfare team reads concerns and plans, and drafts to residents or guardians never include them.
What does Enterprise DNA charge? expand_more
One setup fee, then a retainer for the agreed work. Sam looks at your current StarRez quote, your halls and the reports you rely on before setting the scope. The free version has no licence fee; hosting and agent subscriptions cost what they cost.
What would your own accommodation system look like?
Spend 30 minutes with Sam going through your StarRez renewal, one hall and the checks your team does each week. We agree what to bring across, what to build around it and how we run it for you.
Student Accommodation for Claude Code is free and open source, published by Enterprise DNA.
Done paying for StarRez?
Get your version built