Hosting for vibe-coded HR tools

You build it. We hold the plumbing. Hosting, authentication, permissions, and audit logs for the HR tools your team vibe-coded.

Why vibe-coded HR tools stall

Your team can now build the tools it has 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. The prototype works, everyone likes it, and it needs somewhere real to live. Where does the data sit? Who can see what? How does it reach your HRIS?

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. That is six or seven vendors, and a set of decisions most People teams have no reason to be good at.

So the tool stays a prototype and gets abandoned. Or it goes live on infrastructure nobody reviewed, holding employee data nobody agreed to.

“The build is 20% of the work. Maintenance is the other 80%. Hosting, auth, logs, audit trails, the integrations that break when a vendor changes an API without telling you.”

How you know you're there

  • You built something in Claude, Lovable, or Replit, and it has 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 single sign-on (SSO) and SOC 2.

Vibe-code the rituals, buy the systems of record

Not every HR tool should be vibe-coded. The line isn't drawn by how important the tool feels. It's drawn by the data the tool touches.

Ritual and workflow data
Recognition, sentiment pulses, nudges, reminders, career frameworks. Low sensitivity, small blast radius. Build away.
Sensitive but bounded
Engagement survey comments, 1:1 notes, a reorg draft before it's announced. Very buildable, once you've decided where the data lives and who can see it.
Systems of record
Payroll, compensation, contracts, anything a real decision hangs off. Buy these.

Rituals are the part no vendor fits

The first week. The weekly 1:1. The quarterly check-in. They change shape as the company grows, so the process a vendor sells rarely fits for long.

“Never have I seen the same performance review process work at two companies.”

Joris vibe-coded five tools to show the pattern. Every one is a ritual. Not one is a system of record. They're free: use them, or copy them outright.

For a straight answer on one tool, take the ten questions in Should you vibe-code that HR tool? The whole argument is in Vibe coding for HR: a field guide.

What Pyn holds underneath

You write the tool. We run everything underneath. Hosting, authentication, permissions, and audit logs come built in.

Permissions and sensitive data, handed off

Your vibe-coded tools inherit org chart permissions, managed HR integrations, security, admin controls, and an audit trail. Access rules are enforced at the database level, so people only see what they should.

The HR parts are already built

Built-in employee data, roles, workflows, and messaging mean your tool works end to end, from your HRIS to Slack, Microsoft Teams, and email. These are the blocks every internal tool needs and nobody enjoys wiring up.

What comes with hosting

The database
Infrastructure that already carries a compliance posture. Nobody on your team stands up storage for employee data.
Logins and access control
Single sign-on, with the rules about who sees what kept by the database.
Setup
Deployed and working, not handed over with a link to some docs.
Integrations
Your HRIS, Slack or Microsoft Teams, and whatever else the tool needs.
SOC 2
Evidence you can hand to IT and Legal.
Testing
Someone technical checks the access rules and the login flow before real employee data goes near it.
Light support
When it breaks, you're not the only person who can fix it.

The full offer, and who it suits, is on Managed Hosting.

It stays your tool

Your code stays yours. Open any hosted app in Claude or Codex, make a change, and publish the update when you're ready. Your code, your roadmap. We're the layer underneath.

That matters because the tool will change. Most of the upkeep on a vibe-coded tool is work you can do the way you built it: fix it, tweak it, extend it. What you can't prompt your way out of is authentication, personal data handling, real integrations, and audit logging. That is the part we hold.

The layer underneath has no view on your process, either. We have no opinion about how you should run performance reviews. We think you should have one.

What we don't do

Hosting doesn't include building the tool for you, and we don't host systems of record. Payroll, compensation, and contracts belong in a vendor product.

If you'd rather have the tool built, that is a different service: We'll Build It For You. If yours needs a security review and code hardening before a company rollout, see From vibe-code, to production.

What to tell your security team

Your security team would like a word. Relax, they'll love this one.

They will ask where the data sits, who can see what, how people log in, and what proof there is. On Pyn the answers are short: a database that already carries a compliance posture, org chart permissions, single sign-on, an audit trail, and SOC 2 evidence you can hand over. Pyn is SOC 2 Type 2 certified, and the auditor's report is available on request. Security at Pyn has the detail.

Six practices, and the one we take off your list

Teams that build safely with sensitive data aren't braver than everyone else. They've set up their data flows so risk never accumulates. The field guide names six practices:

  • Don't reinvent compliance. Put the data on a database that is already vetted, and inherit its posture.
  • Collect less. A sentiment tool needs a score and a team, not a name and a manager chain.
  • Tell employees. What you collect, why, and where it lives.
  • Bring Legal and IT in early. At the first prompt, not as a veto at the end.
  • Delete on a schedule. Data you no longer hold is data you can't leak.
  • Keep personal data out of AI APIs. This is the bright line.

Hosting on Pyn takes care of the first. The other five are habits, and they stay with you.

Building it and running it are different questions

“We can't send employee data to AI” mixes up two decisions. When you build a tool, you send code to the model, not employee records, and you develop against synthetic data. The data question arrives at run time, when the live tool reads real records. That is when access control starts to matter.

One thing to say to IT before they say it to you: “it works” and “it's safe” feel identical, and they aren't. Hence the technical check before real data.

Assemble it yourself, or host it on Pyn

Same tool, same code, two ways to stand it up.

Assemble it yourself
About $35 to $60 a month across six or seven vendors, plus $500 to $1,500 for a technical review before you trust it with real data. Once you need single sign-on and SOC 2, the infrastructure alone runs to about $7,500 a year, and the integrations, the testing, and the maintenance are still yours.
Host it on Pyn
From $2,000 a year, plus a one-off setup cost. Setup, testing, light support, single sign-on, and SOC 2 are included.

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.

When to assemble it yourself

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.

The test is one question. Do you have someone who can own logins, access rules, uptime, and integrations, and who will still be there in 18 months? If that person is really “whoever has time”, the maintenance is where it falls over.

The job-by-job comparison is on Managed Hosting.

Start with the tool you already built

Hosting is in early access. You don't need finished code to ask for it.

  1. Check the tool belongs here.Run it through Should you vibe-code that HR tool? Ten questions, and a straight answer on whether to build it, build it with guardrails, or wrap it.
  2. Tell us what you want to host.A tool you've started building, or a new idea you want to build.
  3. Share the code, or describe it.Paste it, upload a file, or describe the tool in a few sentences. An early version is fine, and you can keep editing in your usual tool afterwards.
  4. We set it up and test it.We'll contact you as soon as access opens. From there the tool is deployed and working, with the access rules and the login flow checked before real employee data goes near it.
  5. Keep building.Open the hosted app in Claude or Codex, make a change, and publish the update when you're ready.

Get early access. Bring the tool you've started, or the idea you haven't.

FAQ

Which AI tools can I build with?
Hosted apps open in Claude or Codex for editing. To get started you can share code from Claude, Codex, Lovable, Replit, or GitHub, and an early version is fine.
Who owns the code?
You do. Your code, your roadmap. Open any hosted app in your AI tool, make a change, and publish the update when you're ready. Pyn is the layer underneath.
Will Pyn build the tool for us?
Not as part of hosting. You write the tool and we run everything underneath it. If you want it built for you, We'll Build It For You is a separate service.
What shouldn't we host on Pyn?
Systems of record. Payroll, compensation, and contracts belong in a vendor product. Hosting is for the rituals: recognition, check-ins, nudges, reorg planning, and tools like them.
Does it come with single sign-on and SOC 2?
Yes. Hosting includes single sign-on and SOC 2 evidence you can hand to IT and Legal. Pyn is SOC 2 Type 2 certified, and the auditor's report is available on request.
What does it cost?
From $2,000 a year, plus a one-off setup cost. Assembling the same stack yourself runs about $35 to $60 a month across six or seven vendors, and about $7,500 a year once you need single sign-on and SOC 2.
Can we start today?
Hosting is in early access. Tell us about the tool you've started or the idea you want to build, and we'll contact you as soon as access opens.

Your HR stack, with superpowers.

Pick the tools you need. Launch in a day. Cancel anytime.