What is actually built, and what is not.

Atarla is early. This page says what exists today, what is still being worked on, and how the company got here, so nobody has to guess.

Where things stand today.

Experimental

The prototype

A Raspberry Pi 5 with extra cooling. It is a development machine for testing ideas, not hardware anyone could buy or install.

Pilot

The software

A web application in invite-only testing with a small number of accounts, while the permissions and the workflows get worked out.

Research

The part that enforces the rules

The code that decides what an AI assistant is allowed to do is still being designed and tested. It is the piece everything else depends on, and it is not finished.

Planned

The company itself

Paid for out of Kevin's own pocket, from his own restaurant and local-business experience. An incorporation application has been filed and is still pending.

Nothing on this page is for sale yet. There is no price, no launch date, and no waiting list.

How it got here.

The direction changed several times. The problem underneath it got clearer each time.

  1. 01

    It started as Visible Seed

    The first version tried to help local businesses get better technology and practical help. The idea was right. The shape was wrong.

  2. 02

    Consulting ran into a trust problem

    Custom demos and direct outreach worked, but one-off help is hard to trust and impossible for one person to repeat. Owners who had already been let down by software vendors had no reason to believe another one.

  3. 03

    Software made the work repeatable

    The work moved into software connected to how restaurants actually run, including a phone app that got close to finished before the problem turned out to be bigger than the app.

  4. 04

    Atarla restarted from scratch

    The old code was retired and the company started again around one idea: the business should own the computer that holds its information and decides what its AI is allowed to do.

  5. 05

    A prototype, a private test, and a plan to prove it

    A Raspberry Pi 5 prototype, software in invite-only testing with a small number of accounts, one early customer relationship, and a research plan meant to turn the design into measurable evidence.

What the company is trying to prove.

The business keeps its own information.

What the business knows, and the rules about who can use it, stay on a machine the business controls rather than sitting in someone else's account.

Every assistant has a limit.

Each one gets a job, a list of what it may touch, and a point where a person has to say yes, decided before it is allowed near real work.

Outside help is a choice.

Running things close to the business does not mean never using an outside service. It means using one on purpose, not by default.

See how it is meant to work

A company, not a science project.

The research is how the hard parts get proven: whether owning the machine actually gives a business more control, whether limits on an assistant stay understandable to the person responsible for it, and whether keeping work close is reliable and affordable enough to be worth doing.

Talk about a use case