labs@atheron:~/industries/media$ publish --app --archive --community

Media software

Apps and bots that keep your audience close.

Your audience reads in apps and talks in Discord and Telegram. When either is awkward, they leave. We build the subscriber apps and bots that keep them, assistants that open up your archive, and ledgers that settle who is owed what.

Start a project See the example projects

// what you are up against

The problems we hear most.

Subscribers who quietly leave

Sign-in breaks across devices, the paywall feels like a trap and the app is a wrapped website, so readers cancel without ever saying why.

An archive nobody can search

Decades of stories, broadcasts and footage sit in storage with thin metadata, and finding a clip means asking the one person who remembers it.

Royalties by spreadsheet

Co-producers, distributors and rights holders each keep their own figures, and every statement period ends with a disagreement about the numbers.

The audience lives elsewhere

Loyal fans gather in Discord servers and Telegram channels the company does not run, and subscriber perks never reach them there.

// example projects

Systems we could build for you.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

News subscriber app

Hypothetical. Not a client, not a result.

// The problem

A regional publisher's app is a wrapped website, sign-in fails between devices, and readers cancel without the newsroom knowing which stories kept them.

// What we would build

A native iOS and Android app and a rebuilt subscriber site with one account across both, a fair metered paywall, alerts readers choose, and reporting that shows the newsroom what subscribers actually read.

// What is in it

One account across web and apps, with sign-in that stays signed in
Subscriptions, gifts and student rates through the app stores and the web
Alerts by topic and region that readers choose themselves
Saved stories and offline reading for the commute
Reading reports by section and story for editors
English and French editions from the same system

// Stack

Next.js
React Native
PostgreSQL
Headless CMS interface
Stripe and app store billing
Google Cloud

// estimate

Build: ≈ US$139,000 to US$212,000, delivered within 30 weeksCAD 197,700 to 302,400
Hosting: ≈ US$537 a monthCAD 765 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 9.4 to 15.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.4 to 5.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 39,540 to 60,480
Discovery 9.2%: CAD 18,188.40 to 27,820.80
Design approved 9.2%: CAD 18,188.40 to 27,820.80
Core features 7.6%: CAD 15,025.20 to 22,982.40
Full build 5%: CAD 9,885 to 15,120
First build on devices 20.1%: CAD 39,737.70 to 60,782.40
Testing and fixes 2.5%: CAD 4,942.50 to 7,560.00
Store submission 6.7%: CAD 13,245.90 to 20,260.80
Launch 9.7%: CAD 19,176.90 to 29,332.80
Holdback, 30 days after launch (10%): CAD 19,770 to 30,240

Start from this example

Example projectWeb appAIOpen-source model

Archive search assistant

Hypothetical. Not a client, not a result.

// The problem

A broadcaster holds decades of programmes and stories, and producers spend hours hunting for a clip because the archive only knows titles and dates.

// What we would build

Every programme transcribed and indexed, with an assistant that finds the moment a subject was discussed and links to the timecode. It runs on open-source models on GPUs the broadcaster controls, because unreleased material and rights-restricted footage should not go to an outside provider.

// What is in it

Transcripts for the back catalogue and every new programme
Search by subject, person and place, down to the timecode
Answers that link to the clip and show the rights notes beside it
Speaker and language detection for English and French
An evaluation set from real producer searches, run before every change

// Stack

Whisper (open-source)
Llama or Qwen (open-source)
vLLM
PostgreSQL with pgvector
DigitalOcean GPU

// estimate

Build: ≈ US$109,000 to US$166,000, delivered within 21 weeksCAD 154,900 to 236,700
Hosting: ≈ US$4,530 a monthCAD 6,450 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route: Open-source model
Model running cost: ≈ US$4,190 a monthCAD 5,960 a month

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Specification and evaluation plan: 0.4 weeks
Design approved: 2.4 to 3.9 weeks
Core features: 1.4 to 1.9 weeks
Full build: 0.9 to 1.4 weeks
Working pilot: 3.4 to 5.4 weeks
Testing and fixes: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks
Production: 0.9 to 1.4 weeks

How it is paid

Deposit 20%: CAD 30,920 to 47,280
Discovery 2%: CAD 3,092 to 4,728
Specification and evaluation plan 10.3%: CAD 15,923.80 to 24,349.20
Design approved 2%: CAD 3,092 to 4,728
Core features 6%: CAD 9,276 to 14,184
Full build 4%: CAD 6,184 to 9,456
Working pilot 31.1%: CAD 48,080.60 to 73,520.40
Testing and fixes 2%: CAD 3,092 to 4,728
Launch 2%: CAD 3,092 to 4,728
Production 10.6%: CAD 16,387.60 to 25,058.40
Holdback, 30 days after launch (10%): CAD 15,460 to 23,640
GPU time for training and testing, at cost: CAD 300. Billed up front, at cost, outside the milestones

Start from this example

Example projectWeb appBlockchain

Co-production royalty ledger

Hypothetical. Not a client, not a result.

// The problem

A series made by several production companies is sold in many territories, and each partner keeps its own figures, so every statement period ends in a dispute.

// What we would build

A private permissioned ledger the co-producers and distributor each run a node of, where sales, rights windows and agreed splits are recorded once, with a portal that produces the same royalty statement for every partner.

// What is in it

Deals, territories and rights windows recorded against each title
Sales reports loaded from distributors and checked on arrival
Splits and recoupment worked out from the shared record
The same statement for every partner, with every line traceable
Alerts before a rights window opens or closes

// Stack

Next.js
PostgreSQL
Hyperledger Besu (private, permissioned)
S3-compatible storage
DigitalOcean

// estimate

Build: ≈ US$109,000 to US$167,000, delivered within 23 weeksCAD 155,100 to 237,300
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Architecture: 0.4 weeks
Design approved: 2.9 to 5.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Devnet: 2.4 to 4.4 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

How it is paid

Deposit 20%: CAD 31,020 to 47,460
Discovery 2.5%: CAD 3,877.50 to 5,932.50
Architecture 6.7%: CAD 10,391.70 to 15,899.10
Design approved 2.5%: CAD 3,877.50 to 5,932.50
Core features 7.5%: CAD 11,632.50 to 17,797.50
Full build 5%: CAD 7,755 to 11,865
Devnet 20.2%: CAD 31,330.20 to 47,934.60
Testing and fixes 2.5%: CAD 3,877.50 to 5,932.50
Testnet 13.4%: CAD 20,783.40 to 31,798.20
Launch 2.5%: CAD 3,877.50 to 5,932.50
Mainnet 7.2%: CAD 11,167.20 to 17,085.60
Holdback, 30 days after launch (10%): CAD 15,510 to 23,730

Start from this example

Example projectWeb appBot with a web dashboard

Subscriber community bot

Hypothetical. Not a client, not a result.

// The problem

A podcast network's most loyal listeners gather in Discord and Telegram, but subscriber perks live on the website and moderators check memberships by hand.

// What we would build

A bot for Discord and Telegram that links each member to their subscription, grants the right roles and channels automatically, posts new episodes and alerts, and gives moderators a small web dashboard.

// What is in it

Members link their subscription once, and roles follow it
Perks removed when a subscription ends, without a moderator
New episodes and breaking alerts posted to the right channels
Moderation tools and a log moderators can review
A web dashboard for the community team

// Stack

Node.js
discord.js
Telegram Bot API
PostgreSQL
Next.js
DigitalOcean

// estimate

Build: ≈ US$49,500 to US$75,700, delivered within 16 weeksCAD 70,500 to 107,800
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Commands agreed: 0.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 1.9 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
Working in a test server: 0.9 to 1.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 21,150 to 32,340
Discovery 4.5%: CAD 3,172.50 to 4,851.00
Commands agreed 4.7%: CAD 3,313.50 to 5,066.60
Design approved 4.5%: CAD 3,172.50 to 4,851.00
Core features 13.6%: CAD 9,588.00 to 14,660.80
Full build 9%: CAD 6,345 to 9,702
Working in a test server 9.5%: CAD 6,697.50 to 10,241.00
Testing and fixes 4.5%: CAD 3,172.50 to 4,851.00
Launch 9.7%: CAD 6,838.50 to 10,456.60
Holdback, 30 days after launch (10%): CAD 7,050 to 10,780

Start from this example

Example projectWeb appMobile app

News app redesigned around readers

Hypothetical. Not a client, not a result.

// The problem

A regional publisher's app was built a section at a time; readers say it is hard to find local stories, the paywall appears at odd moments, and subscribers struggle to manage their accounts.

// What we would build

A redesign grounded in reader research: a home screen built around local stories, a clear and fair point where the paywall appears, account and newsletter settings in two taps, built to WCAG 2.1 AA, and a design system your newsroom developers can use.

// What is in it

Research and tests with your own readers and subscribers
A home screen built around local stories
Paywall and account screens that read clearly
A design system your developers can extend

// Stack

Figma
Next.js
React Native
PostgreSQL
DigitalOcean

// estimate

Build: ≈ US$111,000 to US$170,000, delivered within 26 weeksCAD 158,400 to 242,300
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 7.4 to 12.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
First build on devices: 2.9 to 4.9 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 31,680 to 48,460
Discovery 9.2%: CAD 14,572.80 to 22,291.60
Design approved 9.2%: CAD 14,572.80 to 22,291.60
Core features 7.6%: CAD 12,038.40 to 18,414.80
Full build 5%: CAD 7,920 to 12,115
First build on devices 20.1%: CAD 31,838.40 to 48,702.30
Testing and fixes 2.5%: CAD 3,960.00 to 6,057.50
Store submission 6.7%: CAD 10,612.80 to 16,234.10
Launch 9.7%: CAD 15,364.80 to 23,503.10
Holdback, 30 days after launch (10%): CAD 15,840 to 24,230

Start from this example

Example projectWeb app

Video platform that holds on big nights

Hypothetical. Not a client, not a result.

// The problem

A broadcaster's streaming site slows to a crawl on election nights and playoff games, and its small team learns about outages from viewers on social media.

// What we would build

A move of the streaming platform to managed cloud, set up as code, with capacity that grows before a big event and shrinks after, load tests ahead of each one, alerts that reach your team first, and a monthly plan in which we run it.

// What is in it

Infrastructure as code, with staging and production
Capacity planned and load tested before big events
Alerts that reach your team before viewers notice
A monthly operations report and cost review

// Stack

Terraform
Kubernetes
CloudFront
Grafana
AWS Canada

// estimate

Build: ≈ US$46,700 to US$71,400, delivered within 14 weeksCAD 66,500 to 101,700
Hosting: ≈ US$1,360 a monthCAD 1,940 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 19,950 to 30,510
Discovery 6.6%: CAD 4,389.00 to 6,712.20
Design approved 6.6%: CAD 4,389.00 to 6,712.20
Core features 20%: CAD 13,300 to 20,340
Full build 13.3%: CAD 8,844.50 to 13,526.10
Testing and fixes 6.6%: CAD 4,389.00 to 6,712.20
Launch 6.9%: CAD 4,588.50 to 7,017.30
Holdback, 30 days after launch (10%): CAD 6,650 to 10,170

Start from this example

// by service

Go deeper on one kind of work.

Pages for the services we have the most to say about in this industry.

~/apps

Subscriber apps

Native subscriber apps and sites for publishers and broadcasters: one account across devices, a fair paywall, alerts readers choose and reading reports for the newsroom.

~/ai

Archive search AI

Transcribe and index a broadcast or print archive and search it by subject down to the timecode, on open-source models served on GPUs you control, so unreleased material stays private.

~/bots

Media bots

Community bots for publishers, podcasts and studios that link Discord and Telegram members to their subscriptions, grant perks automatically and post new episodes and alerts.

~/chains

Media royalty ledger

A rights and royalty ledger for co-producers and distributors, on a private permissioned chain, so every partner gets the same statement built from one shared record of sales and splits.

// questions

What buyers in this industry ask us.

Do you work with independents and podcasts?

Yes. Several of these examples suit a small team, and the estimator shows the range for your scope.

Can you work with our in-house developers?

Yes. We can build a part of the system and hand it over, or work alongside your team throughout.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the code and the models?

You do, once the work is paid for.

// other industries

Nearby industries.

~/marketing

Marketing and advertising

Campaign dashboards with client portals, brand voice models, impression reconciliation ledgers and referral campaign bots.

See the examples

~/gaming

Gaming

Discord and Telegram community bots, support agents, chat moderation models, tournament apps and player-owned items.

See the examples

~/telecom

Telecom

Field service apps with dispatch, care agents, network alarm models and inter-carrier settlement ledgers.

See the examples

All industries

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

Every market

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call