№ 01
A conversation about your centre
How many rooms, how many sites, what your day actually looks like, and what you are using now. We will tell you plainly if the platform is not a fit yet. It is early, and some things on your list may not exist.
The roll is on paper or in an app that gives up when the wifi does. Ratios are worked out in someone’s head. Consent forms are in a folder, certificates expire without warning, and every parent question goes through the same one person.
For New Zealand early childhood education (ECE) services: childcare centres, preschools and kindergartens, single sites and small groups.
Not a school system with the word “child” swapped in. The roll, the ratio, whānau, consent, compliance, funding preparation and billing, shaped around a room with sand in it and a connection that comes and goes.
Kaiako sign tamariki in and out in a tap. If the wifi drops while the roll is open, a sign-in is held on the device, counted in the ratio immediately, and sent when the connection returns, with nothing counted twice and nothing silently dropped. Two limits: the page has to be open before the connection goes, because it cannot load offline, and the family PIN screen at the door needs a connection.
The adult-to-child count sits above the roll and moves as tamariki arrive and leave, split by age band. Not a number someone reconciles at the end of the week, but a state you can see while the room is still full.
Parents open a browser on their phone and see their own tamariki and nobody else’s: today’s attendance, health information, consent decisions, pānui and messages with the centre.
Conditions, response plans, medication authorities and consent decisions recorded once and shown to the people who need them. An educator can record what a parent said at the door at 8am. That is the moment it matters, not the office’s next quiet hour.
First aid, police vetting, safety checks and practising certificates, each with the date printed on the actual document and who sighted it. The screen flags a date well before it lapses (on screen only for now: nothing emails or pushes the warning), and the system never assumes how long a certificate lasts, because that depends on the issuer.
An applications screen your manager can act on: stages, notes, and an application you can genuinely delete when somebody asks. Nothing feeds it from a website yet. The careers form was taken off in August, and a job application reaches the centre by email for now.
Attendance becomes RS7 preparation figures with the incomplete days shown as incomplete. The system will not produce a total it cannot stand behind, and it never files anything on your behalf. You submit, from numbers you can see the working for.
A draft invoice is editable and an issued one is not. Changing what a family was billed after they were billed it is a different invoice, not an edit. Enforced in the database rather than by a rule in the interface.
In a busy centre, the roll is on paper and the ratio lives in someone's head.
Kindra, from Salix, puts the roll, ratios, families and compliance in one place.
Kaiako sign tamariki in with a tap, and if the wifi drops, the tap waits on the tablet until it's back.
The ratio moves as children arrive, and tells you how many more adults you need.
At the door, families can sign their own child in with their own PIN.
Parents see only their own child, in a phone browser, and can report an absence.
A photo can't reach the whānau journal until the family has given consent.
Medication is recorded against the parent's authority, and a dose outside it is refused.
Staff certificates keep their real expiry dates, and are flagged well before they lapse.
Attendance becomes RS7 funding figures to check and export, and you still submit them.
And privacy is enforced in the database itself, not just on the screen.
Kindra, by Salix. The roll, ratios, whānau and compliance, in one calm place.
A centre holds more sensitive information about a three-year-old than most businesses hold about anyone: where they live, who may collect them, what they are allergic to, and what a court has ordered. That is the part we built first.
Centre from centre, and family from family inside a centre. The second is the one most systems miss: a parent is a role within your centre, so “logged in” must never mean “can see every child”.
Row-level security decides what each request can read, in the database, underneath the application. An application bug cannot widen it, because the application is not what is holding the line.
A suite of isolation tests impersonates an owner, a manager, an educator and a parent and proves each one cannot reach what they should not: around a thousand assertions, run against a real database on every push. One gap we know of: a documentation-only change can deploy before those checks finish. It happened on 26 September, and the checks passed when run straight afterwards.
Consent for a photograph in the learning journal and consent for a photograph on your website are separate decisions, because families routinely give one and refuse the other. Withdrawing consent takes effect immediately: from that moment no new link to the picture can be issued, and a link already open on a screen expires within 15 minutes.
Who changed what, and when, kept as the names of the fields that changed and never their contents, so the log itself holds nothing about a child, and still answers the question a reviewer asks.
A restore drill extracts every table in the main schema, loads it into a fresh schema and compares row counts and a fingerprint per table. It does not cover sign-in accounts, which the database host’s own backup holds, or photos, which are copied separately each day and not yet restore-drilled. A backup nobody has restored is a hope, not a backup.
A childcare platform that oversells is a platform somebody relies on for something it cannot do. These are the four answers we would rather give now than in a meeting.
The ratio bands for centre-based services were checked row by row against Schedule 2 of the regulations on 18 August 2026. A ratio is only as good as its inputs, and the screen says what it cannot see: a visiting child nobody records is not counted. Confirm the figures against your licence, and treat the platform as the place your evidence lives, not as an authority on what the evidence should say.
It prepares the figures and shows the days that are incomplete. A claim built on hours nobody recorded is the one thing a funding system must never do quietly, so it stops and tells you instead.
Every centre is set up with us directly, so the privacy boundaries are in place before a single child’s record exists. That is deliberate, and it is why there is no “start free trial” button on this page.
The whānau and educator experience today is a browser, which works on a phone. An Android build of the native app exists and has run on a test phone, but it has not been released and there is no iOS build, so we are not going to describe it as available.
Every centre is set up with us directly. It is slower than a sign-up form and it is the reason the privacy model is right before the first child’s record exists.
How many rooms, how many sites, what your day actually looks like, and what you are using now. We will tell you plainly if the platform is not a fit yet. It is early, and some things on your list may not exist.
We show you the platform with invented demo tamariki, never another centre’s data. You see the roll, the ratio, the whānau view and the compliance screen with dates already expiring, so you can judge it against your own week.
We create your centre, invite your manager, and check the boundaries before any real record goes in. Nothing about a child is entered until you are ready and your own obligations (insurance, privacy officer, consent forms) are in place.
We also build the centre's public website, the one parents read before they ring. Its forms are not connected to the platform yet: an enrolment enquiry arrives at the centre as an email, not as a record, and nothing on the website can write into the platform. See schools & education for the rest of what we do in this sector.
People you have invited to your centre, at the level you gave them. An educator sees the roll and a child’s health information; custody arrangements are owner and manager only; enrolment details can be read by educators and by the child’s own parents, and only an owner or manager can change them; a parent sees only their own tamariki. It is enforced in the database, and the isolation tests prove each of those separately on every code change.
Staff sign-ins on the roll keep working, as long as the roll was open before the wifi went. The record is held on the device, counts toward the ratio straight away so the room is not shown one child short, and sends itself when the connection returns. It is keyed so a retry cannot record the same arrival twice, and signing out of the app refuses while anything is still unsent, because that queue is the only record those tamariki are in the building. The family PIN screen at the door is different: it needs a connection, and says so rather than pretending.
It is where your evidence lives, and it is not an authority on what the evidence should say. The ratio bands for centre-based services were checked against Schedule 2 on 18 August 2026, and the screen still says what the count cannot know, such as a visiting child nobody recorded. Check the figures against your licence. We would rather say that than let a screen imply a compliance judgement nobody made.
Yes, and you should ask that of anybody. The data is yours: your centre is the agency responsible for it under the Privacy Act and we hold it as your agent. Ask and you get an export.
There is no price list yet, and we are not going to invent one for a page. The platform is early and the first centres are being set up with us directly. Tell us about your centre and we will give you a straight answer for your situation rather than a number that fits a table.
Built and running, with a design partner of two sites shaping it now. Neither site holds any child records in it yet, by their choice and ours, and none will until they are ready to run on it. If you want a platform with a decade of other centres behind it, this is not that. If you want one where the privacy model was built first and you can talk to the person who wrote it, it is.
Still deciding? Read the guide: Choosing ECE software in New Zealand: 12 questions to ask before you sign
We read every enquiry ourselves and reply within two working days. Quick chats, long briefs, half-formed ideas: all welcome.
How many rooms, how many sites, and what your day looks like now. We will show you the platform on invented demo data, never another centre’s, and give you an honest answer about whether it fits yet.