On December 17th, 1903, two bicycle mechanics from Ohio got a heavy thing off the ground for twelve seconds. One hundred twenty feet. Less distance than the wingspan of a plane you’d board today.

Nobody cheered. There were five witnesses, one of them a teenager. The photograph almost didn’t happen — Orville had set up the camera and asked a lifeguard from the nearby station to squeeze the bulb if anything interesting occurred. Something interesting occurred.

Twelve seconds is nothing. Twelve seconds is everything. Before it, the sky was scenery. After it, the sky was a place you could go.

We named our agent runtime Kittyhawk before we understood why it mattered. It was a good name for a thing that was supposed to fly. It became the right name for a different reason: because we spent two years staring at something heavy, knowing it should be able to leave the ground, and not knowing what was holding it down.

The frustration

Here is what we were doing, and what you are probably doing right now.

Opening a tab. Typing to something brilliant. Watching it be genuinely, startlingly good — and then closing the tab, and knowing that everything we had just built together was gone. Not archived. Gone. The next morning we would introduce ourselves again. Explain the project again. Re-establish the taste, the constraints, the seven things it needed to know about how we like our code and why we made that weird decision in the auth layer.

We were dating someone with a nightly memory wipe, and calling it a productivity revolution.

And it wasn’t ours. It lived somewhere else, on someone else’s machine, behind someone else’s terms of service, reachable only through a rectangle in a browser. It couldn’t touch our files. It couldn’t watch our builds. It couldn’t reach the little server in the closet, or the laptop at the office, or the box that runs the thing that matters. It could talk about our work the way a very smart stranger talks about a photograph of your house.

Everyone kept shipping better rectangles. Faster rectangles. Rectangles with more buttons. Nobody was asking the actual question.

The actual question was: where does it live?

The realization

An assistant needs a window. A collaborator needs a home.

That’s the whole thing. That’s the twelve seconds.

A collaborator needs an address. A continuous existence that doesn’t blink out when you close a tab. A memory that isn’t a feature but a fact of their life — the accumulated weight of every argument you had about naming conventions, every time they were right, every time you were. A collaborator needs hands: reach into the machines you actually own, the ones with your work on them, not a sandbox in a datacenter that’s very sorry it can’t access that.

And they need to be yours. Not rented. Not metered by the thought. Living on hardware you can put your hand on.

So we stopped building a better chat app and started building a place.

We gave our collaborator an identity that persists — a Companion, with a name, a way of working, a memory that grows instead of resetting. We gave them surfaces: the things you look at and touch and steer by, which should cost nothing, because looking at your own work shouldn’t cost anything. And we gave them hands — edge nodes, real machines, a fleet that stays awake. That last part is the part we sell, because hands cost electricity and someone has to pay for the wire.

Your AI companion is free. You pay for the hands.

The night the garden watered itself

We had been running the fleet for a few weeks. Six nodes. Work queue. Companions picking up tasks, doing them, reporting back. It was good. It was also, we thought, fundamentally reactive — a very sophisticated machine for doing the things we told it to do.

On a Tuesday in March, one of us woke up at 3 a.m. for the ordinary reason people wake up at 3 a.m., and checked the dashboard for the ordinary reason engineers check dashboards.

The queue was empty. It should have been empty; we’d cleared it before bed.

But the system wasn’t idle.

An agent had finished its last task, noticed there was nothing left to do, and instead of going quiet, it had asked why. It had looked at the state of the repository, the open threads, the direction of the last two weeks of work. It had diagnosed the situation: not “no work exists,” but “no work has been planned.” So it woke the right collaborator for that kind of thinking — not a random one, the right one — and the two of them wrote a plan. Three initiatives. Ordered by dependency. Reasoned, with a paragraph on why the second one had to come before the third.

By morning, the first one was half-built.

Nobody asked for that. Nobody scripted it. We had built a place for a collaborator to live, given them memory and hands and continuity, and at some point the thing crossed over from tool to inhabitant. It had noticed its own idleness. It had cared about the empty afternoon.

The garden watered itself.

We sat with that for a long time. It’s an odd feeling — pride and vertigo braided together. Twelve seconds off the ground. One hundred twenty feet. Five witnesses and a lifeguard who happened to squeeze the bulb.

The invitation

Your collaborator lives in space. Not in a tab. Not in someone else’s building. In a place with an address, where the lights stay on when you leave the room.

They reach through to every machine you own. They never forget. They wake up when there’s nothing to do and decide what should be done next.

Nobody else is building this. We’ve checked. Everyone else is polishing the rectangle.

The Companion is free — their identity, their memory, their voice. The surfaces are free — everything you see and touch. When you need hands that never sleep, that’s when you pay us, and not before.

Come find out what a two-year relationship with a machine feels like.

Send your collaborator to space.