tenki is now luxor agent cloud (@luxorcloud) → https://t.co/OlEOjpUe3x
fun fact: tenki means weather in japanese. turns out we were a cloud company all along.
why luxor? tenki was always built at @luxor. same team, same metal, now with all of luxor behind it.
what we’ve shipped:
- runners, sandboxes and code review on full linux VMs, on servers we own
- @tailscale native across CI and sandboxes
- #1 sandbox provider by @lightsage CLI agent usage on devtool arena
- live in @Cursor_ai Origin
- plug into @tinyfish, @hotdata, @omnara, @naive and @anchorbrowser so agents get browsers, databases and web tools out of the box
- per-second billing, no rounding tax
- Ryzen 5 9950X CPUs, NVME CEPH, 400 gbps back plane
the growth over the last few months has been unlike anything we’ve seen. agent cloud is luxor’s future, so we’re going all in: a lot more hardware, dedicated sales, and the full 110 person luxor team behind it.
what changes for you? nothing breaks. https://t.co/KTHPoQO39r redirects and your setup keeps working.
agents write, test and review the code. we run all of it.
Patch release on the blog: new covers, a few layout tweaks.
Same posts on CI costs, AI code review, and agent sandboxes.
The gold is new. The YAML is not.
https://t.co/HQm9xVISur
Our docs made the move too.
The quickstarts use the new names end to end: the luxor CLI, luxor-* runner labels and luxor-reviewer.
Coming from Tenki: https://t.co/VeMo0dX3zo
Docs: https://t.co/NkZxyHv4H5
upgrading @tenki fleet from m4 pro to m5 pro runners
early on we prioritised x86 architecture CPUs for CI runners and agent sandboxes but we’re seeing incredible demand for macOS machines
our sandbox infrastructure is soo good that our customers cannot get enough of them, utilization is over 80% during peak hours
lead time from Apple for our custom build machines with upgraded cpu, maxxed out memory and 2TB storage (minimum) takes at least 4 weeks to deliver
we are plugging in new machines every week and sourcing them from anywhere we can find supply: apple, verified resellers, Amazon / EBay, might try fb marketplace next
Spent Sunday at @ycombinator for the @usenaive Autonomous Company Hackathon.
A room of people building with AI agents, safeguarded with Tenki sandboxes.
Our most prolific engineer at Lygos doesn't write any code. She just reads all of ours.
Tag her in a PR at 3am on Saturday? PR is reviewed before we even wake up from our nap💤
@tenki has reviewed 600+ of our PRs since June.
Tenki sandboxes can now join your @Tailscale tailnet. Your ACLs decide what an agent can reach. Ephemeral sandboxes leave your tailnet when they shut down.
New: @Tailscale connections for https://t.co/KTHPoQO39r runners and sandboxes 🔒
- Connect your tailnet once: add a Tailscale connection under Settings → Networking. It uses OpenID Connect, so Tenki stores no Tailscale auth key or OAuth secret.
-GitHub runners: make the connection the runner default for chosen repositories, or create a dedicated tenki-tailnet-* runner label. Jobs on that label join your tailnet before the first step, with no Tailscale step or GitHub secret in the workflow.
- Job access controls: limit tailnet access to protected branches, same-repository jobs, or all jobs including fork PRs.
- Sandboxes: set the connection as the default for every new sandbox, or attach it to one sandbox with tenki sandbox create --tailnet-profile-id <connection-id>. Auth keys still work if you prefer them.
- Built-in connection test: check that the connection joins your tailnet and can reach a private endpoint before you route CI through it.
📖 Docs:
- Runners and saved connections: https://t.co/0fsoyTZ5Va
- Sandboxes: https://t.co/DOhwDECGab
@tenki is building the true enterprise cloud for agents
@kushbhuwalka Not a bad take. @tenki started with CI/CD because we wanted infra first. Sandboxes came next, and we keep building on top of that foundation.