An open HRIS, built one tool at a time.

Each tool solves one People-team problem, and the whole stack is yours to read, extend, and own. It starts on the HRIS you already have, with nothing to rip out.

Why your HRIS feels closed

The people data is all in there: start dates, managers, teams, leave balances. Getting it to do anything is another matter. You want a check-in to go out at day 90, or one more field on a form, and the answer is an export, a support ticket, or next year's roadmap.

That is how the category was built. The HRIS began as a ledger for payroll and employee records, and it is good at being one.

“In the 80s, systems like ADP and PeopleSoft introduced the HRIS to better manage complex HR tasks related to payroll and employee records. They were designed for HR (and finance), not for employees.”

Performance and recruiting modules were bolted on later, and each one arrived with the vendor's opinion inside it. Their rating scale. Their cadence. Their fields. Your HRIS knows the day someone becomes a manager for the first time, and most of the time that knowledge stays there until a person on the People team notices and acts on it.

Three ways out

You can wait for the vendor to rebuild it. You can assemble a set of separate tools with Zapier and custom code, and hold the joins together yourself. Or you can keep the HRIS as the record and open up everything that sits on top of it.

This page is about the third.

What open means here

Open doesn't mean a new system of record. Our rule for building in HR hasn't changed: vibe-code the rituals, buy the systems of record. Payroll, contracts, and the employee record belong in a system someone else is liable for. Open describes the layer on top.

Read
Your people data stops being something you export. Pyn reads the HRIS you have, on the fields you choose. Automations run off it, tools draw on it, and an AI assistant can answer from it as the person who asked.
Extend
When the People team hits a problem no module covers, it adds a tool. Install a free one, switch on an automation, or build your own and host it on Pyn.
Own
What you build stays yours, code included. Your HRIS stays the system of record, so nothing here asks you to migrate.

“You don't win by owning payroll. Someone already does, and you shouldn't want to. You win by owning the context layer that sits across everything, the connective tissue that knows who's experiencing what, so every tool you build gets smarter because the others exist.”

What it isn't

It isn't a replacement for your HRIS, and it doesn't run payroll. If you came here to switch systems of record, this is the wrong page. It is also unfinished, on purpose. One tool at a time means some tools aren't here yet.

Built one tool at a time

HR suites are sold whole and adopted in pieces. We build the other way around: one tool for one People-team problem, working before the next one starts. Small and specific beats broad and configurable.

Here is what exists today. All five are free.

Recognition
Dollaroo. Anyone can give a teammate a roo in Slack, tied to your company values. A daily allowance keeps praise meaningful, a rewards shop gives roos real value, and HR runs the program from a Slack command.
A weekly check-in
Team Temperature. A two-minute Slack DM captures a morale score and a few comments. Managers get a weekly digest, and HR sees the company-wide pulse and the teams to watch.
Reorg planning
(re)org. Drag people to reshape reporting lines, compare scenarios side by side, and watch the comp deltas update. It runs in your browser, so a sensitive draft never leaves it.
Career frameworks
Grow. What "good" looks like at every level of a role, with 11 sample role frameworks to adapt.
A quarterly performance check
Drift. It puts the attention on the few people who have been slightly off their game for too long, before that becomes the norm.

Every one of these is a ritual. None is a system of record. Each is designed to hand its data onward, not hoard it, because a tool that keeps its data to itself is an island.

A watercooler for Slack that pairs colleagues from different teams is on the way. It is marked as coming soon in the HR Marketplace, next to everything that already runs.

It starts on the HRIS you already have

No rip-and-replace. Connect your HRIS and it stays the system of record. Pyn connects to BambooHR, HiBob, Rippling, Workday, and ADP, works with Greenhouse and Ashby on the hiring side, and delivers in Slack, Microsoft Teams, or email.

What Pyn reads

You choose the fields. With BambooHR, for example, Pyn syncs name, work email, start date, department, manager, and location by default. You can add any other field, including custom ones, and review the list at any time. Pyn checks for changes regularly, typically every hour, and BambooHR can send them as they happen.

What a change sets off

A change to a field can trigger a message, a poll, a task, or an action in another tool. Set a moment up once and it runs for every person who reaches it, on their own dates. That is automation, and onboarding is the usual first one.

And out again

Any moment can fire a webhook that carries the employee's data to Zapier, n8n, or a service your own team maintains. One event out, and the rest is up to you.

Build the tool nobody sells

Every company has rituals no vendor sells. The first week. The weekly 1:1. The quarterly check-in. They change shape as the company grows, which is why the bought version never quite fits.

Your People team can now build that part itself. Describe the tool in Claude and there is a working version before lunch. The hard part comes after the demo works: where it runs, who can log in, and who sees what.

You build it. We hold the plumbing.

Tools you host on Pyn inherit org chart permissions, managed HR integrations, admin controls, and an audit trail. Your code stays yours. Open a hosted app in your AI tool, make a change, and publish the update when you're ready. Hosting for vibe-coded HR tools is in early access.

Not sure a tool should be built at all? Take the ten questions in Should you vibe-code that HR tool? If you'd rather not build it yourself, we'll build it for you.

Built on an open platform

Everything here runs on the same open developer platform. HR data, behavior, and access are declared once, in code, and the platform is open source, so a developer can read how it works before building on it. If an engineer helps your People team, point them at the developer platform.

Open to your AI assistant, as far as each person is allowed

A stack isn't open if the tools your team already uses can't get into it. That includes AI assistants. Today, getting people data to one usually means pasting an export into a chat.

With Pyn, an admin gives Claude, ChatGPT, or Cursor a permission-scoped way into your workspace. The assistant then answers "who starts next week?" from live data, as the person who asked. Every call runs with that person's own permissions. Your AI assistant only sees what you could already see, and nobody shares a master key. When the assistant does the work as well as answering, that is a headless process.

Open is not the same as exposed

Open describes what your team can do with the stack. It says nothing about who gets to see your people data. That part stays tight:

  • Pyn pulls only the HRIS fields you choose.
  • Customer data is encrypted in transit and at rest.
  • Hosted tools take their access rules from your org chart.
  • Pyn is SOC 2 Type 2 certified, and the auditor's report is available on request. The security page has the detail.

An assistant can tell you who starts next week. It can't tell you what a struggling manager needs to hear. Keep a person on anything a real decision hangs off. If you're weighing AI tools, start with 12 questions to ask AI vendors.

Start with one tool

You don't have to buy a stack to start. Add one piece, watch it work, then add the next.

  1. Install a free tool.Add Dollaroo or Team Temperature to Slack. There is no new tool for anyone to learn.
  2. Connect your HRIS.It stays the system of record. You choose which fields Pyn reads.
  3. Automate one moment.Most teams start with onboarding: set it up once, and every new hire gets it on their own dates.
  4. Build the one that's missing.Run the idea through the ten questions, then build it and host it on Pyn.

Sign up for early access. Bring your HRIS and the one job you wish it did.

FAQ

Does the open HRIS replace our HRIS?
No. Your HRIS stays the system of record, and Pyn doesn't run payroll. The open HRIS is the layer on top: free tools, automations, and the tools your People team builds.
Which HR systems does it work with?
Pyn connects to BambooHR, HiBob, Rippling, Workday, and ADP, works with Greenhouse and Ashby on the hiring side, and delivers in Slack, Microsoft Teams, or email. The integrations page has the full list.
What does open mean if nobody on our team writes code?
You can add a tool without waiting for a vendor's roadmap: install a free one, switch on an automation, or describe the tool you need to an AI assistant and host the result on Pyn, which is in early access. If you do have a developer, the platform under it is open for them to read and build on.
Are the free tools really free?
Yes. Dollaroo and Team Temperature install into Slack at no cost. (re)org, Grow, and Drift are free too.
Who owns the tools we build?
You do. Your code stays yours: open a hosted app in your AI tool, change it, and publish the update when you're ready. Hosting is in early access.
What can an AI assistant see?
Only what the person asking could already see. An admin sets up the connection, every call runs with that person's own permissions, and nobody shares a master key.
What data does Pyn pull from our HRIS?
Only the fields you choose. With BambooHR, the defaults are name, work email, start date, department, manager, and location, and you can review the list at any time. Pyn is SOC 2 Type 2 certified, and the auditor's report is available on request.

Your HR stack, with superpowers.

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