Blog · · 4 min read

Stewardship, not storage: why your business data should stay yours

Your business's records hold years of quotes, invoices, customer letters and decisions. They carry other people's trust as well as your own. An old word fits that job better than "storage": stewardship. A steward looks after what has been put in his care, keeps it whole, and can give an account of it. This post is about what that means in practice when you bring AI into the business.

By Tanner Osterkamp

What is in your control

Very little in business is fully in your control. Prices move, staff leave, vendors change their terms. A few things can be. Where your own records live is one. Who holds the keys to them is another. Whether you can get a complete copy back, on a bad day, without asking anyone's permission, is a third.

Most small offices never decide these on purpose. The mail sits with one provider, the shared drive with another, the invoices in an accounting app, and the customer history on a few phones. Each choice was reasonable on the day it was made. Together they mean the business's memory is spread across companies that do not answer to you, and nobody can say in one sentence where all of it is.

Stewardship starts by making that sentence possible.

What a faithful steward does with data

Put plainly, stewardship of business data comes down to a few habits.

  1. Keep the records where you can point to them. A server in your office that you own is something you can point to. A login on another company's service is not.

  2. Hold the keys yourself. Open the accounts in the business's name, and keep the admin access with a named person in the business.

  3. Keep a copy you have tested. Three copies, one of them offline, and a restore you watched with your own eyes. CISA says backups are the best hope of recovering from ransomware and that recovery should be tested.[1] Our post on the restore test walks through it.

  4. Let a person decide. Software can draft. A named person approves anything that sends, pays, posts or changes who has access, and a person does any deleting.

  5. Be able to leave. If you stop working with any vendor, us included, you should keep the hardware, the files and the memory.

None of this needs a sermon. It needs a list, a machine in a closet that stays on, and someone who checks. The checking is the part people skip, and it is the part that makes the rest true.

Where AI fits

AI makes the question sharper. A model is only as useful as what it can read, so the first instinct is to send everything to it. Kodros goes the other way. The model, the app and the compute run on hardware you own, so when a job runs there, your questions and files are read in your building. A job leaves only for reasons you allow: the local model cannot do it well enough, it is busy, it is down, or a named person sends it out. You can allow none of them.

That is not a promise that nothing ever leaves. Connectors such as email still talk to their own provider, because that is what email is. The point is that you choose, job by job, and the choice is written down.

In practice that means three written answers before the first job runs. Which files may the assistant read? Which reasons allow a job to leave the building? Who approves anything that goes out? Put the answers on one page and keep it with the handover record, so anyone in the business can see what was decided and by whom.

What this costs you

Owning is more work than renting. A server has to stay on. Someone has to look at the backup. A local model can be less capable than the hosted model your staff already tried, and the first year usually costs more than a few rented seats. Our post on renting versus owning has the arithmetic with sources.

What you get for that work is the thing stewardship asks for: you can give an account of what you hold, and nobody else can take it out of your hands.

Questions

Does owning my data mean nothing leaves my building?

No. When a job runs on your own server, the files and questions are read there. Connectors such as email reach their own provider, and you can allow a job to go outside for named reasons. You choose which reasons, and you can choose none.

What do I keep if I stop using Kodros?

The hardware, the files and the memory. The accounts are opened in your name, so there is nothing to hand back.

How do I know the backup works?

Restore a real file from it, open it, and compare it with the original. Until you have done that, you have a copy you hope is good. We run the first restore test with you watching, before you sign acceptance.

Sources

  1. CISA, Back Up Business Data. cisa.gov

What to do next

Kodros puts private AI on hardware you own: the model, the app and the compute, in your building. Every send, post and payment waits for a person. If you leave, you keep the hardware, the files and the memory.

Talk to us Next post: How to make an AI agent ask before it sends, pays or deletes

More to read