Instead of Astalty
Stop paying Astalty per login. Own your NDIS provider system.
We build your version around your registration groups, your roster and the way your coordinators work, bring your Astalty participants, staff and shifts across from its exports, and keep it running for you.
Astalty lists $64 per standard user per month and $30 per support worker per month, GST inclusive, and bills anyone with access whether they use it or not.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the Astalty invoice comes from
Two seat prices, multiplied by everyone who can sign in
Astalty has one feature list and no tiers, which is fair. The bill grows another way: each person with access is a monthly charge, and the extras that make the system talk to participants are metered on top.
Office staff at the standard rate
Admins, rostering staff and coordinators on a desktop are standard users at $64 a month each, which is $768 a year per person before anyone delivers a support.
Every support worker on the books
Each support worker is $30 a month, or $360 a year. Astalty says any user with access is billed by type even if they do not actively use it, so a casual you rarely roster still costs a seat.
Texting participants is metered
2-way SMS is $15 a month for each phone number, then a charge for every outbound message.
Signatures by the piece
Service agreements and forms signed through Astalty cost $1 for every finalised signature request, so each new agreement and each renewal adds a line.
Getting set up costs extra
Self-serve setup is free, but migration packages and customised onboarding are sold separately, and the pricing page gives no figure for either.
Your records on their platform
Astalty has no lock-in contract and offers CSV exports, which is to its credit. The records still live on its platform, and changes to how it works follow its roadmap, not yours.
What your organisation gets instead
The provider record, kept in your own database
Rostering
A roster that holds the line on screening and agreements
The checks run before a shift is booked, not in a report afterwards.
- check No shift for a worker whose NDIS Worker Screening clearance has lapsed on the shift date
- check No shift outside a signed, in-date service agreement
- check A worker cannot be booked in two places at once
- check Short-notice cancellations recorded with their notice period, so claimability follows the rule
Getting paid
Delivered hours that never go unclaimed
The gap between a finished shift and a paid claim is visible every morning.
- check A list of completed, noted shifts with no payment request, oldest first
- check Claims built at the rate in the participant's agreement, so a claim over the price limit cannot be created
- check The bulk payment request file ready for a person to upload
- check Rejected claims stay on the list with their reason until they are resubmitted
Audits
Records an auditor can follow, by design
The rules are written down with their sources, and the strictest ones are enforced when the record is made.
- check A shift cannot be completed without its progress note
- check A reportable incident cannot close until the Commission notification is recorded
- check One check names every breach with the rule and source it comes from
- check Nothing is deleted: participants exit, workers become former, claims stay for the 7 years the rules require
Ownership
Grow the team without growing a seat count
Adding a coordinator or ten casuals changes your payroll, not the cost of the system.
- check No charge per person with access
- check Budgets tracked against pace for each agreement, so under-delivery shows before the plan review
- check Add a field, a support item or a rule by describing it in plain words
- check Open source under the MIT licence, so there is nothing to cancel
Make it yours
Design your own Astalty replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Astalty. 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 Astalty data across and run it for you.
Switching
How to switch from Astalty
A move involves exporting your Astalty records, mapping their CSV columns for import, checking the results, then running both systems side by side before you stop using Astalty.
- 1
Export your Astalty records
Use Astalty’s documented CSV exports for participants, plans, users, shifts, completed shifts and support notes. Include the records and history you need for your day-to-day work. Astalty’s available exports can depend on your account, so check with Astalty if you cannot find a record you need or are unsure what the export includes.
- 2
Map and test the files
Astalty’s CSV columns differ from the layout the free version’s import expects, so the files need mapping before they are loaded. Run the import’s test run first to check how the records will come across. If Enterprise DNA builds your version, they map the files and run the test as part of that work.
- 3
Review the import flags
Treat the import results as a check, not just a count of records loaded. Review what the import flags and resolve issues before relying on the new records. The import can call out shifts without a covering agreement and clients whose funding type was not recorded. Check that key participants, workers, agreements and shift history look right in the new database.
- 4
Run both systems side by side
Keep using Astalty while you check real work in the new system for a short period. Compare participant and worker records, the roster, progress notes, incidents and payment requests so you can find gaps before you stop using Astalty. If workers rely on the Astalty phone app, plan for that change too, since the free version does not include a phone app today.
- 5
Switch off Astalty
When the records and day-to-day checks are satisfactory, stop entering new work in Astalty and use the new system instead. Astalty has no lock-in contract or exit fee, but check your own account and arrangements before closing it. Make the change only after you have reviewed the import flags and are comfortable that the records you need are in place.
Where the real effort goes
The real work is usually mapping Astalty’s fields to the import layout and deciding how much history to bring across. You will also need to check that key details, such as agreements and funding information, are represented as you need them. When you have Enterprise DNA run the move, they handle the mapping and test run.
Not ready for a call?
Get your Astalty switch plan by email
We will send you the step-by-step plan for moving your business off Astalty, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Astalty switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to run it
Run the free version, or have us run yours
Open source
Run it yourself
Free
- 1 Clone the repo from GitHub and run npm run demo
- 2 Open the folder in Claude Code and type /attention
- 3 Export your participants, users and shifts from Astalty as CSV
- 4 Ask Claude Code to map the Astalty columns to the import, then load your own records
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We map your Astalty exports across and check them against Astalty before you switch
- check We shape it to your registration groups, support items and cancellation windows
- check We add a support worker phone app or screens if your team needs them
- check It runs inside Omni, our managed Command Centre, with the rest of your business
Questions
Instead of Astalty, answered
Astalty has no lock-in and no exit fees. Why move at all? expand_more
That makes it easier to leave, not cheaper to stay. The monthly bill still counts every office user and every support worker with access. Your own version has no charge per person, and changing how it works is a sentence to us rather than a feature request to a vendor.
How do our Astalty records come across? expand_more
Astalty lets you export participants, plans, users, shifts, completed shifts and support notes as CSV files. The free version imports a different system's column layout, so the Astalty files need mapping first. We do that mapping and a test run when we build your version, or you can ask Claude Code to map them yourself.
Our support workers use the Astalty app on shift. What replaces it? expand_more
The free version does not include a phone app today. When Enterprise DNA builds your version, a support worker app or simple screens for clocking shifts and writing notes can be part of it.
We mostly do support coordination. Does this fit us? expand_more
It fits best for providers who roster workers, write progress notes, manage incidents and claim for delivered supports. Support coordination features such as a task board and participant check-ins are not in the free version; we would build them into yours if that is most of your work.
Is this compliant with the NDIS rules? expand_more
It enforces the record keeping the rules describe: screening before rostering, notes before claiming, price limits held at the agreement, incident notification before closure, no deletions. Each rule cites its source. Whether a particular incident is reportable stays your judgement, and nothing here is legal advice.
See what your organisation would own instead
30 minutes with Sam. Bring your last Astalty invoice. We count the standard users and support workers you pay for, look at what your team actually uses, and show you what your own version would look like. If it fits, we build it and bring your records across. If not, the free version is yours to run.
Home Care for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Astalty?
Get your version built