Questions and answers
The questions a careful owner asks.
Starting with the four everybody asks about buying software once: updates, support, refunds, and what happens if the company behind it is gone.
014 questions
The questions everyone asks
Do I get updates after I buy?
No. You buy the version that is current on the day you buy, with its source code, and that copy is yours to keep and to change. We send no updates, no new versions and no security patches, ever. If a later version is released it will be a separate purchase, and nothing listed as “not in this version” will be added to a copy already sold. Because you hold the source code, any developer you choose can change it.
Is there support?
No. There is no help desk, no email support and no training, at any price. The reason is simple: it is your software and you are free to change it, and we cannot stand behind changes we did not make. What comes with your copy is help on every screen, 25 step-by-step guides and the written install guide. After that, the person who looks after it is yours: a technical owner, an in-house IT person, or a developer or IT provider on call. We recommend budgeting about $2,400 a year for that.
Can I get a refund?
No. All sales are final. You receive your own copy of the software, including its source code, so we cannot accept returns or give refunds. There is no support and there are no updates. Try the public demo, watch the walkthroughs and read the install guide before you buy. That is also why nothing is sold before general availability, and why everything you need to judge it will be public first: the demo, the recorded walkthroughs, the install guide, the licence and a checker you can run in your own AWS account.
What if you disappear?
Very little changes. You hold the source code and the running system, in an AWS account in your agency’s name, so your copy depends on nothing of ours. There was never a support line or a stream of updates to lose. The licence is perpetual. All you would lose is the chance to buy a later version from us.
027 questions
Buying once
What is the catch with paying once?
There are three. You take on the work a subscription vendor would do for you: running it in your own AWS account, keeping it patched and fixing problems. There is no support, there are no updates and there is no refund. And it is new: no agency runs it in production yet. In return there is no meter. No per-client, per-caregiver, per-user or texting fees, and a price that cannot rise because it is already paid.
How do you make money?
Once per agency: $10,000 for the licence and, if you want it, $1,490 for the install. There is no subscription, no renewal and no paid extra, because we do not sell support, updates, training, data migration or custom changes.
Has any agency used this in production?
Not yet. Hearthway is built and has been demonstrated end to end on a demo agency. No agency runs it in production yet, the installer is still being written, and nothing is on sale until general availability. The demo agency has 40 clients, 24 caregivers and more than 300 visits a week, all invented.
When can I buy it, and what is the launch price?
Not yet. Nothing is sold before general availability, and we will announce that only when the installer and the install guide have been tested on a clean AWS account, the software has been proven in a real agency, an independent penetration test and a restore drill are done, the data loader and the public demo are ready, and counsel has signed off the licence. We give no date. From then the licence is $10,000, or $7,500 for the first 20 agencies or 90 days after general availability, whichever comes first. Join the launch list and you get one email when it opens.
How will we pay?
By invoice and bank transfer (ACH or wire), after you have read the licence and accepted it in writing. There is no card checkout. You will be asked to confirm, separately, that you understand all sales are final.
Can we change the software?
Yes, for your own agency. You receive the source code, and the licence lets you modify it for your own operations. You may not resell it, publish it, share the source or run it for another agency. The source code is confidential: only your employees and contractors who have agreed in writing to keep it so may see it. Changes you make are yours, and yours to maintain.
What if we sell the agency, or open a second location?
The licence is for one agency, one location and one production installation, plus test copies, and it is not transferable. A second location needs its own licence and its own installation. Whether a licence can move with the sale of a whole agency is one of the points counsel is settling. The answer will be in the licence you read before you buy.
035 questions
Installing and running it
Who installs it?
You do, or we do it once. Every licence comes with an installer and a written guide for installing it yourself, at no extra charge. Or you can buy the done-for-you install for $1,490, one time: we deploy the software into your AWS account through a temporary access role, connect email, push notifications and maps, run an end-to-end check with invented data, and hand it over in a recorded 60-minute call. Our access is removed at that handover, and everything after it is yours. The target is 10 business days once your prerequisites are ready. The installer and the guide are still being written, and both must exist before anything is sold.
What does AWS cost?
For an agency of about 40 clients we estimate $30 to $50 a month, paid by you directly to AWS (prices checked October 5, 2026). That estimate has not yet been proven by a live agency, so the install sets a budget alarm at $50 a month. It is the bill of a system someone keeps up to date. An installation nobody maintains costs more; see the next question.
Who keeps it up to date, and what does that cost?
You do, or someone you pay does. We recommend budgeting about $2,400 a year: roughly 20 hours of a developer or IT provider, to do one runtime or database upgrade, apply the quarterly patches to what the software is built on, and fix what comes up. It is $0 in cash if you have that skill in-house. If nobody does it, the system does not only get older. AWS automatically adds an Extended Support charge once the database version leaves standard support, which for PostgreSQL 18 is February 28, 2031: about $146 a month for each database, or $292 with the standby database. The Node.js 24 runtime is forecast to be retired on April 30, 2028; the software keeps running, but AWS then stops accepting changes to it until the runtime is upgraded. And security patches reach your installation only when someone rebuilds and redeploys it.
How do we load our clients, caregivers and schedules?
You load them yourself. A template loader, due at launch, takes your clients, caregivers and contacts from a spreadsheet template. We do not load, clean or convert your data, and we never handle your client records. That is deliberate: your clients’ health information stays with you. There is no import from another vendor’s export, and past visits, invoices and payroll are not brought over.
What if the AWS bill spikes?
The design avoids the usual causes. Screens load when you open them and refresh when you ask, instead of polling in the background, and timers run as one-off jobs. The install sets a budget alarm, $50 a month by default, so you hear about a rising bill from AWS before it arrives. Texts and the automated phone line are the items that grow with use, and both are optional. The one large jump is the Extended Support charge on a database nobody has upgraded.
043 questions
Security and your data
Who is responsible for security?
You are, from the day it is installed. The software is sold as it is, with no warranty and no patches from us. It is built with care for health information: values are encrypted individually, no health information is written to logs, every action is permission-checked and there is an audit trail. What has not happened yet is an independent penetration test or a restore drill on AWS. Both are conditions of general availability, and their results will be published before anything is sold. After you buy, keeping the system patched is part of looking after it.
What about HIPAA?
HIPAA describes how an organisation operates, so it is not a badge a product can carry, and we will not claim one. Hearthway is built for HIPAA-covered agencies and hosted under your own AWS BAA: your agency accepts the AWS health-data agreement on its own account, and your client records never pass through us. There is no vendor BAA, no SOC 2 report and no outside attestation. If you need one of those from your software vendor, we are the wrong choice.
Where is our data, and how do we get it out?
In your AWS account, under your agreement with AWS. We never hold it. You can export the payroll sheet as CSV, the QuickBooks Desktop file, statements and invoices as PDF, and the VA claim file. There is no single “export everything” button in the app. You do not need one: the database is in your own account and you hold the source code that reads it.
055 questions
Fit
Does it handle Medicaid EVV or my state’s aggregator?
No. There is no Medicaid or Medicare billing and no connection to Sandata, HHAeXchange or any state system. Visits are verified by GPS or by phone, which private-pay agencies use for billing questions and families, but that evidence has not been approved for any state program. If most of your revenue is Medicaid, we are not the right choice.
Does it submit VA claims?
It prepares them; you submit them. Hearthway tracks referrals and SEOC authorizations, counts hours used against hours authorized on the VA’s Sunday-to-Saturday week, holds visits that would go over, prepares claims in 15-minute units and produces an 837P file and HSRM documentation packets. It does not transmit to a clearinghouse or post remittances automatically, and neither is in this version. One more thing to weigh: VA Community Care contracts are being re-tendered, and if the rules change, your copy changes only when your developer changes it.
What about QuickBooks and payroll?
For QuickBooks Desktop, Hearthway prepares a numbered IIF file of issued invoices and credit memos that you import and reconcile. Importing that file into a live QuickBooks company has not been tested yet. QuickBooks Online is not in this version, and Xero is not offered. For payroll, it prepares a review sheet and a CSV with regular hours, overtime, commute miles, errands and receipts. It does not pay anyone, withhold or file taxes, and it does not connect to ADP, Gusto or Paychex.
Will my caregivers have to download an app?
No app store is involved. The caregiver app installs from the phone’s browser and opens to four tabs: Today, Shifts, Messages and Me. It is built to keep working without signal: the next seven days are kept encrypted on the phone, and clock-ins wait and sync when signal returns. One honest caveat: offline mode has been built and demonstrated but has not yet been proven on physical handsets in the field. That proof is a condition of general availability.
What about caregivers without a smartphone?
They call the office and the office records the punch, which is checked against the client’s landline caller ID. That is in your copy. An automated phone line, where the caregiver enters a PIN, is built and is connected during installation: by us if you buy the install, by you from the guide if you do not.
Something we have not answered? Ask us. A person reads it and replies once, by email.
Hear when it goes on sale.
One email, when it opens. From then the licence is $10,000, or $7,500 for the first 20 agencies or 90 days after general availability, whichever comes first.
Not on sale until general availability. The launch list costs nothing and commits you to nothing.