Why ONARLY

Connected software for radio, video, sport and media.

Organisations that produce radio, video and sport usually work with many separate tools—for the broadcast, the stats, the team, the files and the website. ONARLY builds these tools as one connected platform: one account, one organisation, one Hub, and products that pass work to each other instead of asking people to copy it across.

ONARLY / WHY ONARLY
01 / THE SHORT ANSWER

Why organisations choose to work with ONARLY.

We are open about where each product stands. Some are ready to use, some are being developed, and some are planned. Every product carries its status.

01

One platform, not a stack of apps

One sign-in and one organisation across radio, video, sport, music and media.

Read more →
02

Built around real workflows

Match-day operation, coaching, live production, station operation and media handling.

Read more →
03

Developed with the people who use it

Feedback, beta testing and partnerships shape what we build next.

Read more →
02 / OUR VISION

One connected platform for creating, producing and sharing.

ONARLY develops software that lets organisations create, produce and share media and run their activities from one connected platform. Our products cover radio, broadcast production, editing, match-day sport operation, team coaching, music creation and media management, with further products in development for websites, commerce, print production and mobility. They share one account, one organisation model and one Hub, so that the work done in one product can continue in the next.

The full story of how ONARLY started and where it is heading will be published here once it has been written and approved by the company.

03 / WHY OUR ECOSYSTEM

What a connected platform means in practice.

Each theme describes the need, how ONARLY responds and the practical value. Labels show whether it is built today or still in development.

01Built today

Connected technology ecosystem

The need
When each tool has its own users, data and login, people spend time moving information between them and keeping copies in sync.
How ONARLY responds
ONARLY workspaces share one account, one organisation and membership model, and one Hub. Products follow a simple rule: one owner per domain—other products hold a reference, not a copy.
Practical value
One place to sign in and manage access, and fewer duplicated files and records.
02Built today

Practical solutions for real needs

The need
Organisations need tools for specific jobs—running a match clock, preparing a practice, switching a live broadcast—not generic platforms they must configure themselves.
How ONARLY responds
Each product is built for a concrete job: match control with score, clocks and venue screens; playbooks, practice and game plans; Preview/Program switching; station decks and automation.
Practical value
Tools that start from the task rather than from configuration.
03In development

Integration between products

The need
The value of one tool often depends on another: a match needs its score on the broadcast; game film needs to become a highlight.
How ONARLY responds
Match state drives the live video scoreboard today. Game-to-replay, clip-to-edit and public team data flows are documented in the ONARLY ecosystem API and are being developed.
Practical value
Work continues in the next product instead of being exported, re-uploaded and re-entered.
04Built today

Flexible product architecture

The need
Organisations differ: a club may need coaching tools but not radio; a station may need radio but not sport.
How ONARLY responds
Products are separate workspaces behind one Hub, each with its own address. Storage is abstracted behind providers such as ONARLY Cloud, Google Drive or S3-compatible storage, depending on configuration.
Practical value
Use the products you need; add others later without introducing a new system.
05Built today

Scalable systems

The need
Tools chosen for one team or one season should not have to be replaced when the organisation grows.
How ONARLY responds
A multi-organisation model with roles and database-level access rules, reused by new products instead of rebuilt for each one.
Practical value
New teams, members and products are added within the same structure.
06In development

Simplified digital workflows

The need
Manual steps between tools are slow and easy to get wrong.
How ONARLY responds
Shared identity, shared media through ASSET MANAGER, and product-to-product handoffs.
Practical value
Fewer manual steps between planning, production and publication.
07Built today

Long-term product development

The need
Organisations need confidence that a tool is maintained and that its status is described honestly.
How ONARLY responds
Products move through documented release gates, status is recorded centrally, and unavailable functions are labelled in the product rather than simulated.
Practical value
You can see what is ready today and what is not.
08Built today

Collaboration with customers and partners

The need
Tools built without their users rarely fit real practice.
How ONARLY responds
In-app feedback for bugs and wishes, the ONARLY Guide, a beta programme and the partnership models on this site.
Practical value
The people who use ONARLY influence what is built and in which order.
04 / WHY OUR PRODUCTS

Every product starts from a specific need.

What each product is for, what exists today and what is still ahead.

ONARLY HUB

Why a unified control centre matters

In development
The need
With several products, people need one place to start, one account and a clear view of what they can access.
Today
Sign-in landing, workspace cards with status labels, search and switching between workspaces, Guide and Feedback.
Next
Cross-workspace projects, assets and activity are shown as empty states until an aggregating service exists.
How it connects
Every ONARLY workspace opens from, and returns to, HUB.
Explore HUB →

ONARLY ARENAHUB

Why clubs and coaches need connected tools

In development
The need
Coaching staff often keep playbooks, practice plans, game plans, film and rosters in separate documents, drives and apps. Keeping them aligned across a season takes time, and players receive material in several places.
Today
Roster, team profile and seasons, playbook, installs, practice and game plans, and film room with clips and angles are built in the application. The hosted backend is not yet deployed.
Next
Schedule, messages, community, scouting, highlights and team pages are being developed. Payments, AI analysis and live replay are planned.
How it connects
Live production and replay stay in BROADCAST STUDIO, highlight editing in DIRECTOR and public team pages in WEBSITE BUILDER—ARENAHUB references them rather than copying them.
Explore ARENAHUB →

ONARLY DRIVE

Why transport operators need an integrated platform

In development
The need
Taxi and mobility operators handle bookings, dispatch, drivers, customer communication and payment—often in separate systems or partly by phone.
Today
A mobility platform for booking, dispatch and drivers, with the QabGo customer app and white-label customer apps built from one codebase and a customer booking API. It is developed as a separate product.
Next
A standalone DRIVE core service is planned. Production release is pending.
How it connects
WEBSITE BUILDER sites can include a DRIVE booking block, verified in a staging environment.
Explore DRIVE →

ONARLY CREATIVE ART

Why clubs could benefit from accessible content tools

Planned
The need
Clubs and organisations need match graphics, social media formats and consistent branding, usually without a design team.
Today
Not built yet. CREATIVE ART is planned as content creation for sport and organisations: brand kits, match graphics, social formats and templates.
How it connects
Planned to use ONARLY match data and ASSET MANAGER media.
Explore CREATIVE ART →

ONARLY PRINTBUDDY

Why print studios need a production workflow

In development
The need
Artwork that reaches a print shop is rarely ready for the machine. DTF, DTG, screen, vinyl and sublimation each have their own preparation steps, and mistakes are often found only after printing.
Today
In development: method-specific preparation, preflight checks (ready, warning, blocked), screen-print colour separation, vinyl cut files, sublimation transfer layouts, plus jobs, machines, materials and cost estimates. ICC colour conversion and soft proofing are not included.
Next
A hosted beta for invited print shops is being prepared.
How it connects
Uses ONARLY accounts and organisations.
Explore PRINTBUDDY →

ONARLY WEBSITE BUILDER

Why a dedicated website experience matters

In development
The need
An organisation's public website often duplicates information that already exists elsewhere—schedules, rosters, booking options—and falls out of date.
Today
In development: the shared ONARLY website engine for branding, templates, drafts, publishing with roles and publication history, with blocks that show live product data. The first block is DRIVE booking.
Next
More templates, multi-page editing, domain provisioning and search-engine rendering are planned.
How it connects
WEBSITE BUILDER owns presentation; each product keeps ownership of its own data.
Explore WEBSITE BUILDER →

RADIO, BROADCAST STUDIO, DIRECTOR, COMPOSER, FLEX, ASSET MANAGER, CHANNEL, OPERA and every other ONARLY product are described on their product pages.

05 / WHY SPORTS ORGANISATIONS

Sports federations: possible areas of cooperation.

Federations differ in size, sport, resources and digital maturity, so there is no single model. Any cooperation would start from the federation's own priorities.

These are possible areas of cooperation. ONARLY has no federation agreement at present.

Possible cooperation areas with sports federations
AreaA need some federations haveWhat ONARLY could contribute
Digital developmentA shared direction for clubs' digital toolsConnected tools and a partner willing to discuss priorities
Club supportClubs with limited volunteer timeReady-made match-day and coaching workspaces
Coach educationConsistent teaching materialDigital playbooks, installs and practice plans as a teaching medium
Video analysisFilm study beyond elite levelFilm room with clips and multiple angles
Player developmentFollowing players across seasonsPermanent player profiles with participation per season
Digital communicationReaching clubs, teams and playersTeam messages and community—in development
Shared resourcesMaterial produced once and reused by many clubsShared playbook and education content—an idea to explore together
Technology adoptionClubs unsure where to startPilots with onboarding and the ONARLY Guide

Member clubs could benefit from tools shaped by their federation's requirements, onboarding through a familiar channel and material that works the same way across clubs. The current sport profile in the ONARLY application is American Football; other sports require further development.

Sports clubs: why connected tools rather than separate ones

Many clubs run their season with a mix of spreadsheets, shared drives, messaging groups, video files and printed plays. Each tool works on its own; the effort goes into keeping them aligned. ONARLY ARENAHUB brings the coaching side of the club into one team workspace, connected to ONARLY's production tools.

How ONARLY ARENAHUB addresses club needs
Club needThe problem in practiceONARLY's approach
Team managementRosters and staff lists kept in several placesPlayers, coaches, team profile and seasons
CoachingCoaching content scattered across filesPlaybook, installs and game plans in one workspace
Practice planningPlans disconnected from the playbookPractice plans next to the playbook they teach
PlaybooksPaper or slide playbooks are hard to keep currentA digital playbook with installs
Video analysisFilm shared as loose filesFilm room with clips and angles
Player developmentHistory lost between seasonsPermanent profiles, participation per season
CommunicationMessages spread across private appsTeam messages and community—in development
Live streaming and replaySeparate streaming toolsLive production in ONARLY BROADCAST STUDIO; ARENAHUB links replays to the game

When the playbook, practice plan and film sit in one workspace, a change in one is visible from the others, and players receive material in one place. When match-day operation and the broadcast share data, the score on screen comes from the same source as the score at the venue.

06 / WHY TECHNOLOGY PARTNERS

Connect at a defined point, not through one-off work.

ONARLY is built around documented boundaries between products, so technology companies can connect hardware, services or data at an agreed interface.

01

Complementary expertise

Partners bring hardware, infrastructure or domain expertise that ONARLY does not build.

02

Technical integrations

Defined integration points: typed control commands, storage providers and the ecosystem API in development.

03

Shared development

Joint specification and testing of an integration before anything is announced.

04

Joint solutions

Packaged offers that combine a partner's product with ONARLY products.

05

Different customer groups

Stations, clubs, producers, print shops and mobility operators.

06

Joint marketing

Announcements and demonstrations under a shared, approved campaign process.

Technology collaborations are presented on the Partners page once both parties have confirmed them.

07 / WHY BUSINESS PARTNERS

Proposed ways to work together commercially.

All models are open for discussion. None of them describes an existing agreement.

Business partnership opportunities
Partner typePossible opportunityPossible model
Distribution partnersOffering ONARLY products in a market or segmentReseller or referral agreement
Commercial partnersPackaged offers for a vertical such as clubs, stations or print shopsJoint offering with agreed roles
SponsorsAgreed visibility at ONARLY events and in ONARLY channelsSponsorship agreement
Service providersOnboarding, training, support or production services around ONARLYService partner agreement
Technology companiesIntegrations and shared solutionsSee technology partnerships

In-product sponsor placements, for example on venue screens or public channels, are not a product feature today.

08 / WHY NOW

The needs ONARLY is designed for.

Not every organisation has these challenges, and not to the same degree. Where they exist, they are what ONARLY's products are designed to address.

Challenges and how ONARLY responds
ChallengeHow it typically appearsHow ONARLY is designed to respond
Fragmented softwareMany tools, each with its own login and dataOne account, one organisation, one Hub
Manual workflowsExporting, re-uploading and re-typing between toolsProduct-to-product handoffs
Coordinating teamsStaff and volunteers working from different versionsShared workspaces with roles
Disconnected communicationInformation spread across private messaging groupsTeam messages and community, in development
Content productionGraphics, video and highlights need specialist toolsBROADCAST STUDIO and DIRECTOR in development; CREATIVE ART planned
Accessible digital toolsTools that need installation, special hardware or specialistsBrowser-based workspaces
09 / WHY TOGETHER

Better tools come from the people who use them.

We want to work with clubs, federations, broadcasters, technology companies and business partners to decide what is built next and to test it in real conditions.

01

Product development

Pilot users show which workflows matter and which do not.

02

Knowledge sharing

Coaches, operators and engineers bring domain knowledge; ONARLY turns it into tools others can use too.

03

Mutual growth

Partners get tools and influence; ONARLY gets validated products and reach.

Example scenario

A club season pilot

A club uses ARENAHUB match control on match days and the ARENAHUB team space for playbook and film during one season. Each month the coaches and ONARLY review what works. At the end, both decide whether to continue and whether to publish a case study.

An illustration, not a description of an existing partnership.
Example scenario

A federation coach-education programme

A federation builds a shared set of installs and practice plans for its coaching courses. Member clubs start from the same material.

An illustration, not a description of an existing partnership.
Example scenario

A technology integration

A hardware company and ONARLY specify how its control surface sends commands through ONARLY's typed command protocol, test it together and announce it only when both approve.

An illustration, not a description of an existing partnership.
Example scenario

A local service partner

A media production company offers match broadcasting to clubs using ONARLY BROADCAST STUDIO and ARENAHUB match control, with ONARLY providing the software and second-line support.

An illustration, not a description of an existing partnership.

Work with ONARLY

Build the next workflow with us.

Tell us about your organisation and the kind of cooperation you have in mind.

Become a partner Partnership models