You can just wake up one day and say “I’m going to change my life” and do it. The world is wide open for anyone with enough agency to do anything they want. This is sick, we live in the best of times. Everything is just working.
GraphQL is a terrible idea. To me, it feels like giving your client direct access to your database. You need a proper API layer with strong boundaries, and gRPC does that pretty well.
I think it might be time to bring back GraphQL.
I helped bring GraphQL to my team at Apple. It was a terrible mistake, probably my worst.
GraphQL has incredible potential, it allows you to organize queries in a way where every client asks for exactly what it wants in combinations no api engineer could ever build all of.
However, because of that, maintaining GraphQL servers is horrible. Building the GraphQL POC worked great, but maintaining it, adding to it, auditing its security was all a continual struggle that was not worth the effort.
Also, humans dont write that much code, so the advantage of custom queries for everyone wasn't too relevant if you weren't Facebook.
But code is cheap now and agents ask for a lot of specific data.
I'm going to benchmark this internally and see what makes sense.
Least privilege is the most high-stakes puzzle in security right now.
The unit of permission is larger than the unit of work, and agents use every permission they get.
Three things I’m seeing right now:
1) Permissions are coarse. GitHub’s “pull requests: write” lets a review agent comment and approve.
2) Controls are fragmented. Every database, API and infrastructure tool has its own authorization model.
3) Access is static. A support agent should lose access to a customer’s records when the case closes. A standing role can’t express that.
Agents reach every one of those systems over the network, so @formalhq enforces least privilege there:
- Every request checked at the level of the action: read these rows, open a PR but never merge it, etc.
- Policies tied to the person or agent acting
- API keys and passwords held at the proxy, never in the agent’s environment
We are proud to partner with some of the best engineering teams working today at Cursor, Decagon, Render, Granola and many more.
DMs are open
“A new Go API for JSON” by Michael Pratt, Joe Tsai, Daniel Martí, Johan Brandhorst-Satzkorn, Roger Peppe, Chris Hines, and Damien Neil — https://t.co/Hyxsj7FQtj #golang