Connect your identity directory
Sync users and groups from Microsoft Entra ID, Cloud Identity (Google Cloud), AWS IAM Identity Center, or the directory that already powers the rest of your access stack—no parallel employee roster.
Most organizations run more than one AI coding product. Seats, access, and usage reporting end up scattered across each product’s admin—easy to drift from the identity directory you already run (Entra ID, Cloud Identity, IAM Identity Center, or similar) and hard to show as one story when people join, move, or leave.
SeatForge connects that directory to Cursor, Claude Code, and GitHub Copilot. You manage access day to day and see the whole picture in one place—without changing how you buy or renew each tool.
Teams pick Cursor, Claude Code, Copilot, and more. The hard part is not buying seats—it is keeping access, lifecycle, and visibility coherent when every product has its own admin.
People and groups stay in your identity directory; contracts and invoices stay with each publisher. SeatForge bridges the gap for access, joiner-mover-leaver, and metrics you can compare across tools.
Sync users and groups from Microsoft Entra ID, Cloud Identity (Google Cloud), AWS IAM Identity Center, or the directory that already powers the rest of your access stack—no parallel employee roster.
Authorize your Cursor, Claude Code, and GitHub Copilot workspaces. SeatForge pulls admin and usage data through each product’s supported APIs—not by clicking through the apps for you.
Map directory groups to entitlements, assign or reclaim paid seats where the APIs allow it, and track adoption and idle paid access in dashboards that span your whole stack.
People and groups live in Microsoft Entra ID, Cloud Identity (Google Cloud), AWS IAM Identity Center, or similar—Cursor, Claude Code, and Copilot each still expose their own admin APIs. SeatForge lines that up so IT and engineering leaders read one coherent story. Okta is the next IdP on the roadmap; tell us what else you need in the pilot.
Need a different provider or platform? Tell us in the pilot form — you'll shape the roadmap.
Real enterprise teams. Real environments. Direct line to the founder.
No contracts, no invoices. I only charge when the product earns it.
I build around your actual environment — not a generic reference arch.
No tickets, no account managers. Fast loops, honest answers, rapid iteration.
Marco van Angeren
Founder & software developer, SeatForge — The Netherlands LinkedIn
"As a developer, I know which agentic IDE you prefer is often a matter of taste. The hard part is what comes next: every provider runs its own admin dashboard, so the work of governing those tools splinters across them. SeatForge centralizes administration for agentic IDE products and connects to Microsoft Entra ID, Cloud Identity, AWS IAM Identity Center, and similar—Okta is on the roadmap—so access management and on- and offboarding stay in one place."
Share your context below. We will follow up directly — no sales team, just the founder building SeatForge. The whole conversation stays fast and honest.