Agents changed how fast we can build software
But shipping still feels slower than it should, because your app, database, deploys, logs, and previews all live in different places
Prisma Compute is our next step toward bringing that whole loop together
New @prisma Compute command of the day: prisma-cli build logs <build_id>
It works with a --follow flag if you want a live tail. Additionally, if you are using Compute through GitHub, your agent can fetch & run it from the Check output.
We shipped a --no-promote flag for prisma app deploy to add more control over deploy promotion.
Fun fact: we're its first users, for one of our services that takes some time to boot. 🧪
The flow:
- prisma app deploy --no-promote
- health-check the candidate
- prisma app promote
Prisma next will also have more intuitive matching of forward and backward relations in cases where they can’t be matched automatically due to ambiguity (explicit inverse fields instead of relation names)
This is how we think infrastructure pricing should evolve as agents take a bigger role in how software is built.
With agents, development runs in tighter, faster loops. More previews, retries, tests, branches, deploys. Pricing has to separate the factory activity from the actual
🇩🇪 Berlin friends, come hang out with us in our office tomorrow at the @typescript Berlin meetup.
We’ll have talks on TypeScript architecture, plus pizza, drinks, and good company.
most Prisma questions i’ve answered over the past couple of years can be solved with the ask ai feature in our docs (built with @kapa_ai).
and if you’re using the prisma mcp, you can ask the same questions directly in your agent and get answers right from the terminal.
"Loops" is clearly the new buzzword. Easy when the flow is local, but when your deployment happens via GitHub, how does your agent know it failed?
@prisma Compute attaches an automated check to every commit. Your agent can fetch it via `gh` CLI and get the full build log.
Wait you guys didn't have websockets? How else would you build something this cool?
Real-time light cycle race with a simple in-memory session and player queue running on Prisma Compute. Have fun✌🏻
gridlock.rtbenfield.dev
A skill should define a contract, not narrate a process.
What goes in. What comes out. What standard it has to meet.
A skill shouldn't read like a blog post. It should read like an interface.
prisma.io/blog/evolving-…
Because @prisma Compute runs on Bun, you can take advantage of Buns powerful functionality for tasks you'd otherwise have to configure an external service for.
Check out how to use Bun.Image to generate thumbnails, and more: prisma.io/blog/image-tra…
At @prisma, we are naturally quite heavy users of Prisma Compute.
Yesterday, I needed to roll back a deployment and didn't find a Console action to do so.
Today, we shipped the "Promote to live" button on each eligible version on Console. Stay safe & keep on deploying!
