About
Who you are actually dealing with.
You are being asked to upload the complete programming of a client's house to a company you have not heard of. That is a fair thing to hesitate over. This page is here so you do not have to guess.
A real company, in one country.
Casient is a small Australian business. It is not a side project behind a domain privacy shield, and it is not a data broker with a free tool in front of it. The registry details are below so you can check them yourself rather than take our word for it.
- Registered entity
- To supply
- ABN
- To supply
- Registered in
- Australia
- Operating from
- Sydney, Australia
- Data region
- Australia (ap-southeast-2)
- Founded
- 2026
Two of those are not filled in yet. We would rather show you an empty field than a number you cannot verify.
Ted
Casient started from a KNX installation that nobody could explain, including the people who commissioned it. The check exists because reading that project by hand took weeks. If you email us, this is who replies.
A distributed group of contributors
Australia and elsewhere. We are not going to inflate that into an org chart. Building the integrator network is the work right now, and answering you directly is the fastest way to do it — so for the moment, one person answers.
The part that matters
What we hold, and what we deliberately do not.
The anxious version of this question is: if I put my client's house into your system, what do you now know about them? The answer is less than you would expect, and that is a design decision rather than a stage we have not got to yet.
- The project files you uploadIn your workspace, under your account. The tool reads them — that is the product. Our staff do not open them, and if you ask us for help and we need to look, you grant it for that job and that session, and it is logged.
- No catalogue of your clients’ housesNo device-level data from a live house is stored in our cloud. The appliance keeps the house's state in the house. There is no central database of what is switched on in your clients' homes, because we did not build one.
- Backups are ciphertext to usIf a client takes the backup service, it is encrypted before it leaves the box and stored in an Australian region. We hold something we cannot read. It restores onto replacement hardware.
- Australian installations stay in AustraliaProjects and backups from Australian houses stay in an Australian region. The control plane is region-complete rather than a single global database with a flag on each row.
- Only the homeowner opens the doorRemote support access is granted and revoked by the homeowner, scoped to a session, time-boxed and logged where they can read it. Not by you on their behalf, and not by us at all.
- A breach here cannot reach a houseThe appliance verifies signatures locally. Compromising our backend does not let anyone push code into somebody's home.
Standards we are working towards.
None of these is held today. This is a list of what we are working towards, published because the roadmap is more useful to you than silence — and because you should be suspicious of a company this young displaying badges. When one is achieved it will appear here as a date and a certificate number, not as a logo.
- A published privacy policy, and the Australian Privacy PrinciplesThe Privacy Act 1988 and the Notifiable Data Breaches scheme are obligations, not badges. This is the first thing to finish and the only one on this list that is not optional.
- ETSI EN 303 645The baseline security standard for consumer IoT — no universal default passwords, signed updates, a disclosure policy, minimised data. It is the right yardstick for a box that lives in somebody’s house, and most of it is already how the appliance is built.
- ISO/IEC 27001The information-security management certification a larger integrator or a commercial client will eventually ask for in a tender. Expensive and slow for a company this size, so it is a goal with a date rather than a promise.
- SOC 2 Type IIWhat partners outside Australia tend to ask for instead of 27001. Same answer: a goal, not a claim.
- KNX Association membershipThe credential this industry actually recognises. Worth naming precisely: the certified KNX bus interface inside the appliance is a certified product, and the appliance as a whole is not a certified KNX product. We will not blur that line.
References, honestly.
There is one installation running Casient and it is in Lindfield, NSW. Every number on this site comes from it, and the check has been run on it in full.
We are not going to list integrators who have not used it. When there are people who have put this into their own projects and are willing to say so, their names will be on this page and you will be able to ring them. Until then this section stays as it is.
In the meantime the strongest reference available is the tool itself. Run it on a job you know inside out and judge whether it tells you something true.
Upload your .knxproj — free
The fastest way to find out whether any of the above is worth believing.
Run the free checkRegister with an email. No card.
Questions about any of this go to [email protected]. If something on this page is wrong or unclear, that is worth telling us — a trust page nobody corrects is a trust page nobody reads.