Back to Building what's next (Interview).
Why Won't Resend Outsource Its Keys?
Zeno Rocha considered WorkOS and skipped it because the team has to own that part. Permissioning and roles could still come from an outside tool, and the problem is still unsolved.
A friend is building an API platform where people can provision API keys. Resend sells API keys to make money, so that work stays inside the company. Handing it to someone else adds another round trip and is going to make access slower. Opening the site in New Zealand might not perform as well as opening it somewhere else. Building a completely new permissioning model makes no sense either. Resend is not here for a new model, but the result has to stay extremely easy.
Someone trying to set up email on a Sunday afternoon, while kids are running, has only 10 or 20 minutes. Get the setup wrong in the 10 or 20 minutes and the person leaves, never comes back, and there is no second chance.
Building what's next (Interview) ·
From the transcript
But WorkOS isn't for really everybody, necessarily. Maybe it is. Maybe it's not. Like, how do you handle this problem? Like, it's not an enterprise problem. It's not a crossing the chasm problem. It's an enabling that we don't want to have to build off, but also get it right for the future the agents demand from us. Yeah, it's really tricky.
Like, the build versus buy decision is always hard. For the all -off layer, for example, we considered using WorkOS. We ended up not because we felt like this specific part, we actually have to own it. But then there are other parts, like the permissioning, the roles. I think we could use something. We're still exploring. We haven't solved the problem yet.