About Kalinklo

Run the week. Manage the engagement.

Kalinklo is where classical music organizations run the week and manage the engagement. Production Desk creates the weekly operating habit; Kalinklo Artist, Agency OS, and the Engagement Ledger connect the people and contracts around that work.

A note from Kalinklo Operations

The first problem is not discovery. It is the private weekly work: schedules, personnel, parts, announcements, confirmations, changes, and the question every staff member asks before rehearsal — who needs what, by when, and have they seen it? Kalinklo starts there, then connects the artist engagement around the same production record.

— The Kalinklo Operations Team

Where the work happens

One OS, two connected engines

Production Desk

Staff manage productions, services, personnel, announcements, confirmations, and red flags for the week ahead.

Member Portal

Musicians see My Week and Next Weeks — their own calls, materials, parts, announcements, and confirmations, and nothing more.

Library Desk

Rights-aware access to the organization's materials — every file carries a rights status, an access rule, and an expiry.

Engagement Ledger

Carries artist engagements from request to hold, quote, contract, invoice, settlement, and archive.

Agency OS

Gives managers and agencies a private desk for roster, routed requests, contracts, invoices, commissions, and presenter relationships.

Principles

How we run the operating system

Private by default

Kalinklo is not a public marketplace. Workspaces, rosters, documents, and engagements open only after reviewed access and explicit permissions.

Access follows the work

A member, substitute, guest artist, agency, or presenter sees information because a role, assignment, production, document rule, or engagement requires it.

Audit on every move

Every material transition writes to the audit log: schedule changes, document access, acknowledgements, holds, quotes, contracts, invoices, and settlements.

Human approval before commitment

AI can draft, summarize, and flag risk. A person approves anything external, legal, financial, or commitment-related.

For whom

One OS, connected by the Production Record

Each audience has a tailored workspace, but the person, production, document, organization, agency, and engagement record connect inside one permission model.

Organizations

Orchestras, festivals, opera companies, conservatories, and ensembles run the week through Production Desk and My Week.

Agencies

Managers keep their artists, brand, and relationships while Kalinklo handles the operational backend.

Artists & ensembles

Artists keep a professional identity, availability, repertoire, media, and engagement history connected to organizations and agencies.

Presenters & institutions

Presenters and institutions request holds, manage seasons, compare terms, and keep a private record with the artist side.

Boundaries

What we are not

Defining the boundary is as honest as defining the product.

We are not a public gig marketplace

Kalinklo is built for classical music operations, weekly production access, and serious engagements that require discretion, approval, and a record.

We do not replace every incumbent on day one

Kalinklo can coexist with Tessitura, OPAS, ArtsVision, Drive, Dropbox, email, and accounting tools while it proves the weekly Production Desk workflow.

We do not force public profiles

Artist visibility is configurable. Represented artists can stay private, stealth, or workspace-only; public discovery is opt-in.

We do not replace agents

If an artist has representation, requests route through the agent. Agency OS gives managers the backend without taking their public relationship away.

We do not custody money by default

By default Kalinklo records obligations and settlements; money moves bank-to-bank or via your existing processor. Custodial paths require a separate contract.

We do not let automation commit for people

Drafts, summaries, and flags are useful. External messages, contracts, invoices, settlement changes, and legal or financial commitments require human approval.

Roadmap

What ships, when

We commit to dates only when the work is in motion. Items beyond Q4 are direction, not promise.

Shipped
Reviewed access and engagement workflow
Artist, agency, presenter, and organization workspaces open after review; request, hold, quote, contract, invoice, and settlement records stay audited.
Shipped
OS-first public positioning
Production Desk and My Week become the public wedge while Kalinklo Artist and Agency OS remain connected engines in the same OS.
Pilot target
One concert week through Kalinklo
A founding organization runs one production week with staff view, member view, documents, announcements, acknowledgements, and a post-pilot report.
Next
Library and Command Center hardening
Rights-aware document access, readiness scoring, red flags, and production-week support mature around real pilot usage.

Reviewed access

Ready to run one concert week through Kalinklo?

Give us one week. We help set up a private staff and member portal, migrate the weekly materials, invite the roster, and show who has seen and confirmed the work.

Request access Explore Production Desk