Hosting your vibe coded HR tools
You build it. We hold the plumbing.
Top brands trust Pyn





The offering
Your team can now build the tools it's wanted for years. A recognition ritual, a check-in flow, a reorg planner, an onboarding nudge that actually fires. Describe it, and it exists by the end of the week.
Then comes the part nobody warned you about. Where does the data live? Who can see what? How does it reach your HRIS?
We handle that part. You keep building.
The pain it solves
Every HR team stalls at the same point. The prototype works, everyone likes it, and then it needs somewhere real to live.
Doing that properly means a database, logins, access rules so a manager sees only their own team, integrations, SOC 2 evidence, and someone to own it all afterwards. Six or seven vendors, and a set of decisions most People teams have no reason to be good at. We mapped the whole stack, tool by tool, in our field guide to vibe coding for HR.
So the tool either stays a prototype and gets abandoned, or it goes live on infrastructure nobody reviewed, holding employee data nobody agreed to.
Who this is for
- You've built something in Claude, Lovable or Replit, but it's been stuck for a month.
- Your team wants four or five internal tools, and you don't want four or five infrastructure projects.
- IT or Legal asked where the data sits and you didn't have a clean answer.
- Only one person understands how it runs, and you worry about them leaving.
- You want SSO and SOC 2.
Not sure whether your tool should be vibe-coded at all? Run it through the "Should HR vibe this" Assessment. Two minutes, and a straight answer on build, wrap or buy.
What it is
You write the tool. We run everything underneath.
- The database. Infrastructure that already carries a compliance posture.
- Logins and access control. SSO, with rules enforced at the database level so people only see what they should.
- Setup. Deployed and working, not handed over with a link to some docs.
- Integrations. Your HRIS, Slack or Teams, and whatever else it needs.
- SOC 2. Evidence you can hand to IT and Legal.
- Testing. Someone technical checks the access rules and login flow before real employee data goes near it.
- Light support. When it breaks, you're not the only person who can fix it.
It stays your tool. Your code, your roadmap. We're the layer underneath.
What we don't do: build the tool for you, or host systems of record. Payroll, comp and contracts belong in a vendor product.
The economics
$2,000 a year, plus a one-off setup cost.
Assembling it yourself runs $35 to $60 a month across six or seven vendors, and closer to $660 once you need SSO and SOC 2. Plus a technical review at $500 to $1,500 before you trust it with real data.
| To do | Assembled: pull together toolsVendors: 6–7 | Bundled: setup, hosting, complianceVendors: 2 |
|---|---|---|
| Vibe the code | Claude Code | Claude Code |
| Keep versions of the code | GitHub | GitHub |
| Somewhere to run it | Railway | Pyn |
| Store the data | Supabase | Pyn |
| Log people in | Supabase Auth + Google | Pyn |
| Control who sees what | You write and maintain the rules | Pyn |
| Single sign-on (SSO) | Supabase Team tier | Pyn |
| SOC 2 / ISO 27001 | Supabase Team tier | Pyn |
| Run things on a schedule | Railway | Pyn |
| Connect to your HRIS data | You build and maintain it | Pyn |
| Connect to Slack or Teams | You build the app | Pyn |
| Send email | Resend | Pyn |
| Know when it breaks | Sentry | Pyn |
| Domain | Your own domain (~$15/year) | Your own domain (~$15/year) |
| Technical review | Hire a contractor to review it | Included |
| Support | You, or whoever built it | Light support included |
| Continuity | Open question | Ongoing |
| Setup cost | Budget $500 to $1,500 for a security review | One-off setup |
| Running cost, no compliance | $35 to $60/month (~$700/year) | From $2,000/year |
| Running cost, with SSO + SOC 2 | ~$630/month (~$7,500/year) | Included |
| Number of vendors to manage | Six or seven | Two |
| Best when | Technical capacity to vibe and manage infrastructure | Focus on the vibing without the plumbing |
The monthly number was never the expensive part. It's the weeks of setup, the vendor accounts, the integration work, and the question of who owns this when the builder leaves.
Worth being straight about the trade. If you only need the basic tier and someone on your team enjoys this work, assemble it yourself. It's cheaper and you'll learn more. Once compliance enters, you're paying $7,500 a year for infrastructure alone and still doing the integrations, the testing and the maintenance.
Your HR stack, with superpowers.
Pick the tools you need. Launch in a day. Cancel anytime.