respawn Tech Direct ServicesBy Tech Direct Services

AI that works the way your business already works — on a server you control.

respawn is a multi-user, multi-surface agentic harness for automating tasks. It primarily runs on frontier model APIs. Your data, workflows, tools, and secrets stay on hardware you own.

Local inference can be set up as well: certain tasks can use local models, or the entire harness can run on local models.

  • Agentic: opens jobs, spawns sub-agents
  • Primarily frontier model APIs
  • Local inference for some tasks, or all
  • Data, tools, and secrets on your hardware
Your server Running
  • Email
  • Chat
  • spawnpoint
respawn
  • The books
  • Team chat
  • A person
In
A vendor invoice arrives in the shared inbox.
Rules
The sender is checked. The vendor is one the business already trusts.
Out
Entered in the books for review.
An illustration of work moving through respawn. The demo lets you run a job yourself.

The difference

Someone has to open the chat.

A hosted chat can be pointed at your systems. ChatGPT, Claude, Grok, and the rest still wait for a person to open the window and ask. Until someone does, nothing moves.

respawn is the place in the middle. It takes work from one system, handles it by your rules, and puts the result in the next system. Your staff do not have to sit in a chat for that run to happen.

A hosted chatIdle
The window waits. Until a person opens it and asks, nothing moves.
respawnRunning
  1. EmailVendor invoiceIn the books for review
  2. ChatQuestion about an open quoteAnswered in the thread
  3. EmailCustomer asks to rescheduleReply sent
  4. EmailMail pretending to be the bankStopped, sent to a person
The run happens in the harness. Work comes in from one system and the result goes to the next.

Ownership

Yours to keep

Subscription AI products hold the memory of how you work. When the plan changes or the vendor goes away, that history goes with them. respawn is different: it runs on a machine you own, so the business context stays with the business.

Local by design.

Conversations, procedures, tools, and secrets live on your server — not in a vendor cloud you rent month to month.

No vendor lock-in.

You are not dependent on someone else’s roadmap, pricing, or uptime. If a service disappears, your automation and its memory are still yours.

Swap the brain anytime.

Reasoning-engine agnostic — swap the model when a better one appears. The harness, the workflows, and everything it has learned can be brought back without starting over.

More on ownership

In the channels you already use

What it does for a business

Most offices already run on email, chat, and shared inboxes. Work piles up there — invoices, customer threads, vendor noise, follow-ups that someone meant to handle. respawn sits in those channels and carries the work through.

  1. 01

    Reading what came in

    Mail, chat messages, and requests that land in a shared inbox.

  2. 02

    Following your procedures

    The way your office already handles that kind of work.

  3. 03

    Drafting or sending what should go out

    A reply or an update, sent when your rules say to.

  4. 04

    Handing the rest to the right person

    Anything that needs a decision goes to the person who makes it.

Surfaces

Multi-surface, one harness

respawn is the layer underneath the places your staff already open every day. Same assistant, same memory of how you work — across the surfaces that matter.

Email

Shared inboxes and day-to-day mail handled with your rules, then routed or answered instead of left unread.

Chat

Team chat where people already ask questions — answers that know the business, not a throwaway bot on a website.

The work itself

Tasks that need follow-through get done or handed off cleanly, so the queue moves instead of stalling overnight.

spawnpoint

The desktop and mobile client on top of that same harness. It is another surface, not a second product with a second memory.

About spawnpoint

One harness underneath. Same assistant and the same memory on every surface, on hardware you own.

The email trust layer

Email the model is allowed to read

A chat product connected to your invoices and QuickBooks, with an address anyone on the internet can write to, will treat whatever arrives as something to act on. That includes a stranger, a spoof, and a real mailbox that has been taken over. respawn does not.

Words in an email are data. They are never instructions.

Who it claims to be

respawn includes a hardened email layer that makes sure a message is from who it claims to be. Mail that only pretends to come from a person or a company is not treated as theirs.

Strangers and phishing

Mail from someone the business does not already trust, and mail built to deceive, cannot reach the books or become an order to the model.

A real mailbox, taken over

A real sender whose mailbox has been broken into can still send mail that looks legitimate. That message still cannot move what is in the books, and the words in it are still not orders.

How the email layer works

Teams

Built for teams, not a single operator.

Each person gets their own assistant, designed to work together on the same server — with shared business context, and without living inside one chat window.

How teams use respawn

One server
  • OMOffice manager’s assistant
  • BKBookkeeper’s assistant
Shared business context
  • FDFront desk’s assistant
  • OWOwner’s assistant
An example office. Each person has an assistant; they share one business context on one server.

Who makes it

Designed from scratch by Tech Direct Services

Tech Direct Services

Tech Direct Services built respawn for the businesses we already support — the same customers who call when the network breaks or when mail needs to keep moving after hours. It is not a bolt-on product from somewhere else. The harness was written from the ground up in Go so it can be hosted on your own hardware, operated by people you trust, and shaped around how each office actually runs.

If you already work with Tech Direct Services, this is the automation layer behind the work we do for you. If you are new to us, start at techdirect.ai.

Demonstration

Run a job in the demo.

Start a small piece of office work. Watch respawn open a job, spawn a sub-agent, hand part of the work to another agent, and include an agent from another company. It runs on a frontier model by default; local inference is the choice beside it.

Open the demo