What’s new in Rabt
Accounts you can actually administer
Signing out now ends the session on the server, passwords can be reset three different ways depending on who is asking, and a platform administrator can edit a user without going near the database.
- Sign out ends the session server-side, so a stolen session token stops working immediately rather than at its own expiry.
- Sign out everywhere, from your own account page, ending every other device.
- Three password flows: you change your own, you forget yours and reset it by email, or an administrator resets someone else’s and hands over a temporary password.
- Editing a user: name, phone, role, status and brokerage, with the last active super administrator protected from being demoted, suspended or deleted.
- Deleting a user releases their email address, so somebody moving from one brokerage to another can be added again.
Releases without dropped requests
Rabt now deploys blue/green: the new version is built and health-checked on a second port before any traffic moves, and the old one stays on disk ready to take over again.
- Zero-downtime deployment. Measured across a release: 150 consecutive requests, all 200.
- Rollback is a service start and an nginx reload — seconds, with no rebuild.
- A pre-deploy check refuses any migration that would break the version still serving, because both versions talk to one database during a switch.
Load an insurer pack from the browser
A whole insurer pack — rate charts and tables of benefits — can be imported from the inventory screen instead of a shell, and the importer will tell you what it is going to do before it does it.
- Upload an insurer’s pack and have the rate grids read out of it, age band by age band.
- A dry run reports every row it would create, so nothing is written until you have read what it found.
- Scanned documents up to 20 MB, which is what a real licence scan weighs.
Network is a join key, not a field
A plan and a network are separate things that combine, so one plan on three networks is now three quotable offerings rather than three near-duplicate plans you have to keep in step by hand.
- Plan variants, network tiers and co-pay blocks combine into quotable offerings, derived rather than stored.
- Changing a benefit once changes it for every network that plan is sold on.
- Clear filters on every list screen.
A front door
Rabt has a public site, and a brokerage can ask for access from it without emailing anybody.
- A request form that lands in a queue platform staff work from inside the console.
- The brand system — the mark, the lockup and the type — applied across every screen.
- Contrast fixed across the design system’s colour tokens in both themes.
Related
See it on your own rate charts
Rabt is not a demo account with somebody else’s plans in it. Load one insurer’s rate chart and table of benefits, and quote from them the same day.