We're giving startups $50K to build on @tenki.
But credits only matter if the product underneath is worth using, so here's what you'd actually be building on:
Sandboxes. Disposable VMs where your AI agents write and run code in real isolation. Spin one up in seconds, per-second metering, throw it away when the agent is done.
GitHub Runners. Change one line in your workflow file, get builds ~30% faster at up to 60% less than GitHub's.
AI Code Reviewer. Reviews every PR with your whole codebase in context, so nobody on the team is the review bottleneck.
If you're an early-stage team, this is compute you're already paying for somewhere. Now it's covered.
$10K free, then Tenki matches 1:1
→ $10,000 in credits to start.
→ Every dollar you spend after that, matched 1:1 up to $40k Buy $40k, walk away with $80k
For startups that haven't raised beyond Series A. Applications are rolling, we reply within a week.
📫 https://t.co/Ej0GgHuzuq
Big news — I've joined @tenki to lead DevRel.
And I'm kicking it off by ignoring finance's advice and giving startups $50K of credits for sandboxes, code review, and CI runners.
Tell your founder friends. Ask me anything.
We're giving startups $50K to build on @tenki.
But credits only matter if the product underneath is worth using, so here's what you'd actually be building on:
Sandboxes. Disposable VMs where your AI agents write and run code in real isolation. Spin one up in seconds, per-second metering, throw it away when the agent is done.
GitHub Runners. Change one line in your workflow file, get builds ~30% faster at up to 60% less than GitHub's.
AI Code Reviewer. Reviews every PR with your whole codebase in context, so nobody on the team is the review bottleneck.
If you're an early-stage team, this is compute you're already paying for somewhere. Now it's covered.
$10K free, then Tenki matches 1:1
→ $10,000 in credits to start.
→ Every dollar you spend after that, matched 1:1 up to $40k Buy $40k, walk away with $80k
For startups that haven't raised beyond Series A. Applications are rolling, we reply within a week.
📫 https://t.co/Ej0GgHuzuq
Every npm install runs code you've never read. 403 packages, 8 vulnerabilities, scripts from dozens of authors. Run it all in a sandbox. None of it touches your machine.
Big news: Kimi-K3 by @Kimi_Moonshot is now #1 in the Frontend Code Arena with 1679 pts, surpassing Claude Fable 5.
This is a 17-place jump from Kimi-k2.6 (#18 -> #1).
In Frontend, Kimi-K3 ranked #1 in 6 of 7 domains: Brand & Marketing, Reference-Based Design, Data & Analytics, Consumer Product, Simulations, and Content Creation Tools, landing #2 only in Gaming behind Fable 5.
The full model weights will be released by July 27.
Congrats to the @Kimi_Moonshot team on this major milestone!
Biggest thing we've learned this year running coding agents in the cloud: output quality depends less on the model than on whether the agent has a real dev environment, the same one a developer would have locally.
Locally you never think about this. The agent just inherits your laptop's setup. In the cloud you rebuild everything from scratch, and you can't tell when you've gotten it slightly wrong.
Because nothing crashes. You just get output that's a bit worse than it should be. Most people don't notice, and the ones who do blame the model.
Nine times out of ten the agent simply couldn't run or verify its own work.
A year ago this didn't matter, models couldn't use an environment anyway. Now they can, and the environment is usually the bottleneck.
Your most expensive bug is the zombie microVM that keeps charging you because your .kill() line never ran.
Sandbox teardown should be bound to scope, not to a cleanup call you hope executes.
If your SDK supports context manager, defer, or await using, use them. If it doesn't, that's a gap worth paying attention to.
Leaking a sandbox should be structurally impossible.