The front door
Amplify
Hosts the SML TV website and automatically scales when more people visit.
A proposal for the Client · the Company
Your platform.
Your customers.
Built to grow.
SML TV would give the Company its own place to sell live events, subscriptions, and replays—without handing the customer relationship to another video platform.
Built for live
One simple idea
AWS runs the machinery.The Company owns the business.
The proposal in plain English
Not another embedded player. A Company-owned streaming business.
The public website is only the front door. Behind it is one Company system that knows the events, customers, purchases, subscriptions, and exactly who is allowed to watch.
We would use managed AWS services instead of a room full of servers. That keeps the platform scalable, reliable, easier to maintain, and more cost-aware because the expensive live-video pieces can run only when they are needed.
From the control room to the viewer
One protected signal path, explained simply.
The blue and amber paths represent two separate contribution feeds. If one feed or network path fails, the second is ready to carry the show.
- 01Production
The Company creates the live program.
- 02Two SRT feeds
Primary and backup take separate paths.
- 03AWS video services
AWS receives, converts, and prepares the stream.
- 04CloudFront
The stream is distributed close to viewers.
- 05SML TV
Approved customers watch on their screen.
The part that matters most
The Company owns the audience relationship.
01
Customers create a Company account.
02
The Company records purchases and subscriptions.
03
The Company decides who can watch each event or replay.
04
Future web, Apple TV, Roku, and mobile apps use the same account.
The AWS service lineup
Specialists, not servers.
Each AWS service has one job. Together they form a managed stack, which means less equipment for the Company to patch, secure, and babysit.
01
Platform stage
The customer experience
The storefront, customer accounts, and the business rules behind every purchase.
The account desk
Cognito
Handles sign-up, login, password resets, and secure customer sessions.
The control desk
API Gateway + Lambda
Runs the rules for events, purchases, access, replays, and administration.
The master record
RDS PostgreSQL
Keeps the Company’s customer, event, purchase, subscription, and access records.
02
Platform stage
The live-video path
The broadcast machinery that receives, converts, prepares, and delivers the show.
The protected handoff
MediaConnect
Receives primary and backup SRT feeds and provides the contribution path into AWS.
The format converter
MediaLive
Creates several video qualities so each viewer gets the best stream their connection supports.
The stream organizer
MediaPackage
Prepares live video for secure, reliable delivery to web players and future apps.
The delivery network
CloudFront
Moves video closer to viewers so playback starts quickly and stays stable.
03
Platform stage
The support crew
Storage, system health, and protection working quietly behind the live experience.
The media library
Amazon S3
Stores artwork, files, and replay assets in scalable cloud storage.
The system lookout
CloudWatch
Tracks platform health, records activity, and raises alarms when something needs attention.
The front-line guard
AWS WAF
Helps protect the website and APIs from abusive or malicious web traffic.
One sensible exception:
A dedicated payment company would securely process credit cards. The Company would still own the customer account and viewing-access record.
Early planning estimates
Ready when quiet. Pay more when live.
These rounded numbers are for conversation and planning only. They are not an AWS quote and must be replaced by a detailed calculator model before pricing a customer event.
Quiet month
$75
estimated / month
The website, accounts, database, security, and monitoring remain ready. Live video services are stopped.
One live event
$100
estimated before viewers
A quiet month plus about $25 for one two-hour live event. Viewer delivery is added separately.
1,000 viewers
$240
estimated total
One two-hour live event with roughly 1,000 complete viewer sessions.
10,000 viewers
$1,500
estimated total
One two-hour live event with roughly 10,000 complete viewer sessions.
Simple planning shorthand
$75 base + about $25 per two-hour event + about $0.14 per two-hour viewer session
Real cost changes with picture quality, event length, viewer location, replay use, security choices, and the percentage of viewers watching each quality level.
The storefront stays ready.
The website, account system, database, artwork, protection, and monitoring remain available. Live contribution and encoding should be stopped so they are not billing as running channels.
The video machinery switches on.
The Company starts the redundant contribution, live encoding, packaging, and delivery path. Cost then follows event hours and audience usage.
Development partnership
A clear working arrangement, with no surprises.
Development will move through practical milestones with regular communication, transparent invoices, and approval before expenses.
Standard development rate$120/hr
Company preferred rate$60/hr
50% preferred-rate discount for this project
Milestones along the way
Work will be divided into practical milestones that are defined and scheduled as the project develops. Priorities, expected work, and the next decision will stay visible.
Weekly, detailed invoices
Development will be invoiced weekly on Net 14 terms. Each invoice will identify the work completed, time spent, current milestone, approved expenses, and relevant project details.
Owner-controlled expenses
AWS and other third-party services will be created under Company-owned accounts using the Company’s payment method. The purpose, expected cost range, and alternatives will be discussed with the Client first. Nothing that creates or materially increases an expense will be activated or purchased without the Client’s approval.
Communication throughout
I will stay in direct communication with the Client throughout the process so decisions, progress, costs, risks, and upcoming work remain clear.
A careful path to launch
Build the business rules first. Prove the broadcast path before selling it.
- 1Define version one
Choose PPV, subscriptions, replay windows, admin needs, and expected audience size.
- 2Price the exact design
Build a dated AWS estimate for the chosen video quality, redundancy, event length, and viewer scenarios.
- 3Build development and staging
Create the customer, event, payment, access, and playback experience away from production.
- 4Test like a real show
Break feeds, lose networks, test payments, challenge access controls, and load-test real playback.
- 5Launch with human approval
Production changes remain controlled and reviewed by the Company.
The opportunity
A professional platform that carries the Company’s name—not somebody else’s.
Start with live web PPV. Keep the foundation ready for subscriptions, replays, Apple TV, Roku, mobile apps, and a second delivery network later.
Review from the top