Back to KORA

The technical side, in plain words.

Everything an owner or their IT person might reasonably want to check before putting a machine from another country on the office network. No jargon that hides an answer, and nothing claimed that has not been built.

KORA

KORAIf something here reads like a promise I cannot keep, tell me and I will take it off the page. This is the half of the website that has to survive a technical person reading it slowly.

KORA — her presence rising as green light out of the Core

Why I exist at all

Built for our own company first, sold second.

Every part of this started as something we needed ourselves. The follow-up nobody had time for. The documents that had to be checked before they went out. The same question asked for the fourth time that week. We built the thing that carried it — and only once it was doing that every day did it become something we could put in a box. Then the businesses around us started asking whether we could build them the same thing. That is how KORA became a product — asked for, not invented in a boardroom.

The problem we actually had

A small company where everything important passed through one person. Growth did not make that better; it made it heavier. More clients meant more coordination, and coordination is the part nobody wants to hire for.

Why not a cloud assistant

Because the work we wanted taken off us was the work that repeats — and paying a metered model to re-read the same business every time is the one shape that gets more expensive as you succeed.

Why a machine of its own

The reading, sorting and checking runs on hardware we already paid for. What we could not do locally, we routed out deliberately — and wrote down exactly when that is allowed.

What that means for you

The limits on these pages are not marketing caution. We are the first business that has to live with them, which is why they are written plainly instead of hidden in a footnote.

What I was built to fix

The work that comes back every week.

  1. Follow-up that never goes outthe list, sorted by what is at stake
  2. Documents checked by hand, every timechecked against a rule instead
  3. The same question answered again and againanswered from what you approved
  4. Information living in five different systemsread across all of them
  5. Someone leaves and takes the method with themthe method stays with the business
  6. A new person who takes weeks to become usefulthey ask me, not you
  7. Nights and weekends doing nothingthe machine is already paid for
  8. Growth that costs another administratorthe coordination stops scaling with headcount

How work gets done

Every task goes down this ladder, in this order.

I do not send every task to the most capable model. I take the cheapest route that will do the job properly, and only step up when the job genuinely needs it.

  1. Ordinary software — a script, a rule, an automationno AI cost
  2. My own model, running on your Corenothing leaves
  3. An AI subscription your business already pays forwhere the provider allows it
  4. An inexpensive outside modelpaid per use
  5. A strong outside modelwhen quality needs it
  6. A premium modelrare, high-cost-of-error work
  7. Once the task repeats, it stops being an AI task at allit becomes a process

You pay outside providers directly, at cost, for what was actually used — there is no markup and there are no KORA credits. Monthly ceilings can be set for the company, for a role, or for one person.

The straight version

What I do, and what I will never do.

✓I do this

  • Spend as little of your money on AI as the job allows. I do not pay an expensive outside model where ordinary software, a rule, or my own local model is enough. Every task goes down that ladder first, and the ordinary understanding work runs here, on hardware your business has already paid for. Premium intelligence is for the part that genuinely needs judgement.
  • Read and understand the documents, mail and records your business already has.
  • Answer your team from the rules and decisions you approved.
  • Draft quotes, documents, replies and follow-ups in your own wording.
  • Carry work between the systems you already use, without replacing any of them.
  • Turn work that repeats into a process that no longer needs a model at all.
  • Keep working at night and at weekends on everything you have already approved.

×I will not do this

  • Act just because I can reach something. Access is not authority — you draw the line.
  • Send, publish, pay or delete on my own. Anything that leaves the company waits for a person.
  • Tell you nothing ever leaves your office. That is not true of any capable system, and you set what may go out.
  • Guess. If the evidence is not there I say “I do not know” in those words, and what it would take to find out.
  • Replace your CRM or your accounting. I work on top of them.
  • Charge you a markup on outside AI. You pay the provider directly, at cost.

The machine

One chassis. Three capacities.

All three Cores are the same machine. What changes inside is how much work can run at once, which is why the line-up follows team size rather than features.

Core 
Solo1–3 people
Team4–10 people
Team Plus10–30, or several businesses
Memory 
32 GB
64 GB
96 GB
Storage 
1 TB
1 TB
2 TB
On-board AI 
Included
Included
Included
Upgradeable 
Yes, in place
Yes, in place
Yes, in place
The Core's edge, etched with the client company's nameIt arrives with your name on it. Etched, with a code that opens your own setup.
The opened box: the Core, one cable and one cardThree things in the box. The Core, one cable, one card — and nothing else.
The Core standing on a working deskIt sits where you work. No rack, no server room, no fan you can hear.

Memory and storage go up inside the same Core as the team grows — no upgrade fee, and no new licence; you pay for the parts. Three-year manufacturer warranty on the hardware. Several businesses run as separate sealed compartments on Team Plus, at no extra charge.

Your data

What stays in the building, and what does not.

Where the work happens

The everyday work — reading, sorting, drafting, checking against your own rules — runs on the Core in your office, on hardware you own.

When something goes out

I will not tell you nothing ever leaves. When a task genuinely needs the strongest outside model, I say so. You decide in advance what may go out and what may never.

Access is not authority

Being connected to a system is not permission to change it. Each person has their own working context, their own limits, and their own budget.

Nothing irreversible without a person

Sending, publishing, paying and deleting always wait for a human confirmation. That is a design decision, not a limitation we are working around.

One business, one KORA

Your KORA is yours. It is not a workspace inside a shared system, and it has no way to read another company’s Core — even if the same person owns both.

If you stop paying

The Core, the data and everything already learned stay on your machine. The managed service around it stops. Come back and it continues from the same place, with no reactivation fee.

KORA

KORAI would rather lose a sale than write “nothing ever leaves” on a page. What I can promise is that you decide what goes out, in advance, and that I say so when a task needs it.

Getting started

From the box to working: five steps.

  1. You approve the configuration and the total in writingnothing charged before this
  2. The Core is configured for your business before it shipsnot assembled by you
  3. It arrives: the Core, one cable, one cardabout two to three weeks
  4. Plug it in, scan the code, connect the sources you allowyour rules, your limits
  5. We talk, and the service starts billing from that daynot from the order date
The edge of the Core, etched with the company name and a setup codeThe night is working time. Everything you approved keeps running while the office is closed.
KORA pinned at the top of the messenger the team already usesNo dashboard to open. After setup I am pinned in the messenger your team already has.

Starting on a Friday is a recommendation, not a promise: the Core reads quietly through the weekend so Monday does not begin with an empty chat. How long a full first read takes depends on how much history the business has — there is no artificial limit and no fixed number of hours we will claim.

What the $300 covers

Keeping a working system working.

Updates and security

The system and its components are kept current, including security updates, without you scheduling anything.

Tested models only

New models are validated before they ever reach your Core. You get a tested improvement, not the newest thing on the market.

Routing that keeps getting cheaper

When a better or cheaper route appears, the same work starts using it. That is the part of the service that pays for itself over time.

Skills and libraries

Proven capabilities are added as part of the service. There is no separate charge for a new workflow.

Support without a counter

Unlimited tickets. The Core diagnoses and maintains itself first, and opens a ticket when a person is genuinely needed.

People, seats and budgets

The first person is included. Each additional person is $99 a month or $699 a year, with their own permissions and their own AI ceiling.

Still a question left

Call me. I will answer everything.

Including the technical ones. If the honest answer is that your business does not need me yet, that is what you will hear.

Call KORA

Or go back and tell us in writing what keeps going wrong.

A phone showing an incoming call from KORA, her waveform glowing green on a black screen

Some people want to build a corporation. Others don’t, and we want them to have that choice.

EMAILkora@vigogroup.ca
TALK TO MEStart with what is broken
WHERE

Canada & United States

© 2026 KORA