←
Luxor Agent Cloud2,234 posts
Luxor Agent Cloud avatar

Luxor Agent Cloud

@luxorcloud

Cloud infrastructure for code and AI agents: Sandboxes, Runners, and AI Code Reviewer. Built by @luxor.

◷ Joined January 2025▧ 151 Photos and videos
Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 16

Tenki is now Luxor Agent Cloud. Same team, same bare metal, new name tag. The story from @guzmanpintos:

tenki is now luxor agent cloud (@luxorcloud) → luxor.ai 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. tenki.cloud redirects and your setup keeps working. agents write, test and review the code. we run all of it.

0:17
Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·21h

Day two as Luxor Agent Cloud. Here's the 30-second tour:

0:30
Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 13

We don't rent the future, we rack it. More machines, newer silicon: now on M5 Pro. Your CI just got faster.

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

Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 11

Sandboxes aren't the only thing that's ephemeral. Merge soon.

0:12
Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 6

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.

Guzman Pintos @guzmanpintos Nov 6 Your sandbox can now join your Tailscale private network Stop punching holes in your network for AI agents. Past few weeks have been incredible for growth but also to receive invaluable user feedback. We started noticing that a few teams hit the same walls.

Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 5

Private networking for your CI and your agents, built on @Tailscale. Don't let Black October become Black November.

New: @Tailscale connections for tenki.cloud 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: tenki.cloud/docs/runners/tai… - Sandboxes: tenki.cloud/docs/sandbox/tai… @tenki is building the true enterprise cloud for agents

Guzman Pintos avatar
⟳ Luxor Agent Cloud retweeted
Guzman Pintos@guzmanpintos·Nov 4

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.

Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Nov 2

This trick needs more visibility

Guzman Pintos @guzmanpintos Nov 2 We split our CI into 2x more jobs. That's why it got 4x faster. Our goal was that every job in our pull request (PR) workflows finishes in about 60 seconds. Our slowest TypeScript job took 226 seconds. Now every TS job finishes in under 60. Our slowest Go jobs got

Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Oct 30

Billed by the second, not by the minute.

A CI job that runs 2m56s and a fraction gets billed 2m57s on @tenki runners. Queue time isn’t billed. The VM is destroyed when the job ends, so billing stops there. Agents open a lot of short PRs. Rounding every job up to the minute adds up.

Luxor Agent Cloud avatar
Luxor Agent Cloud@luxorcloud·Oct 29

Leo is winning us over with that orange-gold color-way... 😉

I had my agent benchmark this against my current CI provider (@tenki) At the moment choosing Vercel CI doesn't make sense as it's slower in most cases, and more expensive. But it will only get better from here! 🫡

Post attachment