Amela
RaceCast Inc. — A New Platform Launch Story
ℹ︎ For confidentiality, company and project names and system images have been replaced with pseudonyms and mockups.

Race predictions,Auto-delivery from zero.

RaceCast is a prediction-delivery platform for public-racing fans, handling everything from automated race-data collection to prediction delivery and P&L management. It processes 8 venues nationwide and 300+ races a day unmanned.

Data collection, prediction delivery, instant reach, and P&L visualization — the story of launching a new platform, built in-house from zero in 6 months, that satisfies all four axes essential to public-racing prediction delivery at once.

Auto collection
300 / day+ races
Patrol all venues with the crawler
Delivery automation
100% unmanned ops
Automated collection → prediction → delivery
Instant reach
Telegram Push
Reliably delivered just before cutoff
P&L logging
100% auto-tallied
Visualize hit and payout rates
RaceCast · Delivery Feed
Finalized predictions before cutoff
Higashi-Chuo R11 8 min before cutoff Confidence A
3rd Higashi-Chuo Memorial
5 8 12 Predictions 6.4
Ryokufu R10 Hit +8,200
Quinella ③-⑦ / Anchor ③
Today's P&LPayout rate 112%
01
CLIENT
About the client

RaceCast — a leading domestic name driving public-racing predictions.

RaceCast Inc. runs a service that delivers race predictions to public-racing fans. Covering 8 venues nationwide and over 300 races a day, it delivers finalized predictions to users just before each cutoff.

The business model is a prediction-delivery subscription. Users receive predictions via Telegram and manage their betting P&L in the app. Delivery freshness and hit reliability drive continued use.

Per day
300+
Auto-collected races
Crawl support
8venues
Nationwide venues
Delivery automation rate
100%
Unmanned ops
BUSINESS FLOW
1STEP 1
Auto-collect race information
The crawler patrols all venues to fetch race information
2STEP 2
Auto-generate predictions
Analyzes collected data and assigns bet selections and confidence
3STEP 3
Deliver anchored on the cutoff
Scheduler + queue work backward from the cutoff time
4STEP 4
Instant delivery + P&L logging
Instant push via Telegram, betting P&L auto-recorded
02
CHALLENGE
Design challenges to solve

Four structural requirements demanded of the platform.

None of these are technology-selection problems; they are business requirements tied directly to delivery freshness, reach rate, continued use, and reliability. A ground-up build required a design that satisfies them all at once.

Collecting vast race information
Tallying nationwide races by hand for each race day300+ per day volume of data would break operations. An automated-collection design becomes a prerequisite.
Cutoffs that differ per race
Cutoff times differ per race, and matching delivery timing by handDelays and missed deliveries are inevitable occur. Time-anchored automation is required.
Reliable reach before the cutoff
Relying on email or on-site posting means users miss predictions before the cutoff.Arrives instantlyWithout designing the delivery path, value never reaches users.
P&L visualization
Leaving hit-rate and payout-rate tallies to users fails to convey value and drives churn.Automatic betting-history logging must be built into the platform.
03
ARCHITECTURE
The architecture we built together

Turning prediction delivery into a platform that never stops, across four domains.

Against four design challenges, we built the collection, prediction-delivery, instant-reach, and P&L-visualization domains in-house from zero. An automated operating loop anchored on cutoff times delivers predictions with no human intervention.

Amela
EXECUTION
6months
Duration
30person-months
Total effort
Domain ①
Data collection
Challenge
Need to collect nationwide race information for each race day
Solution
Auto-collect all venues with the crawler
Schedules from the cutoff and retries on gaps
Domain ②
Prediction generation & delivery
Challenge
Need to deliver in time for each race's differing cutoff
Solution
Scheduler + queue auto-execute anchored on the cutoff
Parallel prediction generation → delivery with Bull/Redis
Domain ③
Instant reach
Challenge
Need to reliably deliver predictions to users before the cutoff
Solution
Instant push just before cutoff via Telegram bot
Delivery workers broadcast to targeted users
Domain ④
P&L visualization
Challenge
Need to continuously tally users' hit and payout rates
Solution
Auto-records betting history and visualizes it on a dashboard
Real-time tallying of hit rate, payout rate, and P&L trends
Frontend
Next.js (PWA) React Tailwind CSS
Backend
NestJS MySQL Redis / Bull
Infra & Delivery
AWS S3 / SES Telegram Bot Scheduler / Worker
04
IMPACT
The value the platform creates

RaceCast's unmanned operation, accelerated.

This platform continuously produces business outcomes — delivery freshness, operational efficiency, continued use, and reliability — rather than technical metrics.

A platform that delivers in time for the cutoff
Cutoff-anchored automation delivers predictions for every race without delay.
Scale up with zero operational effort
Everything from collection to delivery runs unmanned, so scaling up events adds no headcount.
A design that maximizes retention
Instant reach and P&L visualization underpin the user's reason to keep using it.
Operations that can focus on reliability
Crawl monitoring and retries detect gaps, ensuring delivery coverage.
🎯
STAKEHOLDER
General users
The prediction recipients
Generally
Pressed by cutoffs, users end up hunting for predictions themselves.
At RaceCast,
Finalized predictions arrive on Telegram automatically just before cutoff
Bet decisions with no missed opportunities
Drives higher retention
🛠️
STAKEHOLDER
Operator
The delivery operators
Generally
Race tallying and prediction delivery tend to be handled manually every race day
At RaceCast,
Collection → prediction → delivery run automatically, unmanned
Scaling with zero operational effort
More events without more people
STAKEHOLDER
Delivery platform
Dev & ops team
Generally
Peak-time broadcasts are prone to congestion and delay
At RaceCast,
Parallel distribution via the queue for stable delivery at every cutoff
Every race delivered without delay
Stable operation even at weekend peaks
🔍
STAKEHOLDER
Data quality
Delivery reliability
Generally
Collection failures translate directly into missed deliveries
At RaceCast,
Crawl monitoring + retries detect gaps
Ensures delivery coverage
Improved service reliability
05
DEMO
Three scenarios

Experience RaceCast with a live, working demo.