Manifesto

Most records systems in this sector were bought to satisfy a funder rather than to serve the community that owns the records. They sit somewhere else, on terms nobody in the building wrote. We build the opposite. One governed record, on hardware in your building, administered by your own staff, with an audit trail you can read without asking us. Everything we ship has to survive losing the connection, losing us, and losing the person who set it up. 

Most records systems in this sector were bought to satisfy a funder rather than to serve the community that owns the records. They sit somewhere else, on terms nobody in the building wrote. We build the opposite. One governed record, on hardware in your building, administered by your own staff, with an audit trail you can read without asking us. Everything we ship has to survive losing the connection, losing us, and losing the person who set it up. 

Most records systems in this sector were bought to satisfy a funder rather than to serve the community that owns the records. They sit somewhere else, on terms nobody in the building wrote. We build the opposite. One governed record, on hardware in your building, administered by your own staff, with an audit trail you can read without asking us. Everything we ship has to survive losing the connection, losing us, and losing the person who set it up. 

Benefits

What we hold ourselves to.

Six positions we do not trade away. Written down here so you can hold us to them.

Nothing leaves the building

Storage, the database, search indexing, character recognition and model inference all run on the appliance. No part of serving a request needs an outbound connection.

You can always leave

Export in documented, non-proprietary formats, on a defined timeline, at no charge. The obligation sits in the customer agreement rather than in a policy we can revise.

Your staff administer it

Accounts, groups, permissions, the tag vocabulary, rules, backup and updates are yours. A platform only the vendor can operate is a dependency dressed as a service.

Our access is scoped and logged

Named account, scoped to an incident, recorded in the same audit trail you review, revocable by you without reference to us. No standing administrative access.

Nothing trains across Nations

Each deployment's model learns only from that deployment's record. That rules out pooled training and any central improvement loop. It is slower, and it is not negotiable.

We say what is not built

Deployed, in development and specified mean different things and we use them differently. The gaps are written down, and we will show you the list before you sign anything.

FAQs

Questions?

If the answer you need is not here, ask us directly. We would rather answer it once, properly.

Something not covered here?

Ask us directly.

Talk to us

Talk to us

Who is Tsen'awt for?

Indigenous governments and institutions in Canada: First Nations, Tribal Councils, Indigenous organizations and economic development corporations. The reference configuration is a First Nation government. The other segments differ structurally rather than cosmetically, and each needs its own base configuration.

Do you write the software yourselves?

What do you refuse to build?

Who holds the encryption keys?

What if we have no technical staff?

Is there a certification we can point a funder to?

Can a Tribal Council run one system for its member Nations?