How migration works
We move records, materials, and workflows carefully with your people—usually 7–14 days of joint effort.
See MigrationKalinklo OS · Product
One operating system. Two connected engines.
Run the Week handles production operations. Manage the Engagement handles guest-artist, agency, and presenter work. The Production Record connects them.
The architecture
Two engines, joined by one record.
The week and its engagement are two engines reading and writing one Production Record, so contracts and the services that need them stay connected.
Engine one
Run the Week
Production operations: services, personnel, materials, announcements, confirmations, and readiness.
Explore the desksThe bridge
The Production Record
The shared record connecting the production week to its guest engagement.
Engine two
Manage the Engagement
Guest-artist, agency, and presenter workflows from request through settlement and archive.
Explore the desksThe desk map
Every desk, one click away.
Run the Week
Production Desk
Productions, services, call times, personnel, materials, announcements, confirmations, and readiness.
Member Portal
Each musician sees their own calls, materials, parts, announcements, and confirmations.
Personnel Desk
People, sections, roles, substitutes, assignments, and time-limited access.
Library Desk
Rights-aware materials with access rules and expiry.
Command Center
Production-week risks linked directly to their fixes.
Season Desk
Plan the season, then turn the plan into the week.
Manage the Engagement
Engagement Ledger
One record from request through hold, quote, contract, invoice, settlement, and archive.
Agency OS
Private roster, routed requests, contracts, invoices, commissions, and relationships.
Kalinklo Artist
Professional identity, availability, repertoire, media, and engagement history.
Contracts & Invoices
Versioned quotes flow into contracts, invoices, settlements, and archive.
Who it is for
Start from your seat.
Organizations
Orchestras, festivals, opera companies, and conservatories run the week.
Read moreAgencies
Managers keep their roster, brand, and relationships while Kalinklo runs operations.
Read moreArtists
Artists keep professional identity, availability, and engagement history.
Read moreInstitutions
Presenters plan seasons, place holds, route approvals, and keep private records.
Read moreEvery ensemble
One engine, in your ensemble's language.
Kalinklo adapts its vocabulary while the operating model remains consistent.
| Ensemble | Who leads | Members classified by | The roster |
|---|---|---|---|
| Orchestra | Conductor | Instrument / section | Orchestra |
| Opera company | Music Director | Discipline / role | Company |
| Conservatory | Director | Department / instrument | Community |
| Chamber ensemble | Artistic Director | Instrument / chair | Ensemble |
| Festival | Artistic Director | Role / project | Festival |
The same engine supports choirs, bands, and theatre pits. Vocabulary and section presets adapt without forking the operating model.
How it lands
Migration and trust, answered.
How trust works
Reviewed access, least-privilege permissions, auditable records, and rights-aware materials.
See Trust CenterReviewed access