Who is Twine for?
Twine serves two main groups: End customers are companies that use Twine to keep their HR and payroll systems in sync. A typical setup might read employee data from an HRIS and push it to a payroll system, an identity provider, and a time tracking tool - automatically, without manual data entry. Vendor customers are HR tech companies that use Twine as an integration hub to access their customers’ data through Twine’s public API. Instead of building individual integrations with every HR system their customers use, they integrate once with Twine and get access to normalised, structured data across all of them.What makes Twine different?
- Independent and flexible - Twine is not tied to any single vendor. Any supported system can act as a source, and those with write capabilities can act as a destination.
- Low-code transformation - Data can be shaped and transformed using Twine’s Data Engine without writing custom code for each integration.
- Date-tracked data - Twine’s data model is built around when values take effect, not just what the current value is. This makes it possible to represent historical data and future-dated changes accurately - provided the source system exposes that history.
- Nordic focus - Built around the systems and workflows common in Nordic HR and payroll environments.
Where to go next
Key Concepts
The core ideas behind how Twine models and moves data.
Integrations
All systems Twine connects with, organized by category.
Platform
Data domains, domain mappings, sync triggers, and the data engine.
API Reference
Full API reference for vendor customers building on top of Twine.