Cartcast
Live shows, in-video checkout and shoppable replays, as an embed for merchant sites — on live-commerce infrastructure you own.
Cartcast is live-commerce infrastructure a brand drops into its own store through a lightweight embed: live shows, checkout inside the video, and shoppable replays — on the brand's own site, with the brand's own audience.
The buying moment stays inside the experience the merchant already owns.
Live commerce loses its advantage when the audience has to leave the show to complete a purchase. Interest is immediate, but the handoff to another tab turns a shared moment into a conventional checkout journey and gives hesitation time to return. The same break appears after the broadcast: attention earned during the event fades if the recording becomes passive content. For a merchant, the cost is not only a missed order. It is a channel that demands hosts, promotion, and production while sending the highest-intent viewers through the least coherent path.
- Live shopping broadcasts
- In-stream checkout
- Real-time engagement (chat/reactions/pins)
- Multi-host shows (LiveKit)
Every live-driven sale becomes explainable revenue for the right merchant.
A platform serving multiple merchants can look healthy in aggregate while quietly creating a finance problem for each one. Products drift out of sync, orders need manual interpretation, fulfilment teams wait for context, and commission calculations become arguments after the show. The operator pays twice: first in support time, then in merchant trust when payouts or attribution cannot be explained quickly. Growth makes the weakness more expensive because every new tenant adds another catalogue, another settlement rhythm, and another set of people asking which number is authoritative.
- Product catalog & variants
- Cart, orders & fulfillment handoff
- Commission billing
- Merchant payouts (Stripe Connect)
- CSV/Shopify import
- Instant payouts
Each show leaves evidence the next campaign can use.
A live show produces plenty of activity and very little clarity unless the operator can separate noise from commercial signal. Hosts remember the busiest minute, merchants remember the product they expected to win, and teams often plan the next event from anecdotes rather than evidence. That creates a cycle of repeated timing mistakes, weak product sequencing, and spend that cannot be tied back to revenue. The business cost is compounded uncertainty: nobody knows which format deserves another campaign, which audience is returning, or where attention consistently disappears before the sale.
- Basic analytics
- Advanced analytics (heatmap/cohort)
- AI insights (Claude Sonnet 5)
Automated operations scale without turning every integration into manual work.
When the core platform cannot participate in a wider operating stack, every cross-system workflow ends with a person copying data. That manual seam is easy to tolerate for one merchant and expensive across dozens: launches slow down, records diverge, and routine updates compete with customer work for the same attention. Agencies and technical operators then carry an integration tax on every new account, even when the surrounding systems are already automated. The business consequence is a ceiling on scale set by handoffs, not by demand or product capacity.
- Programmatic + agent API (Connect + MCP)
Multi-host shows — a second presenter, a guest, a brand collaboration — are available on the higher tiers.
Most of a show's total revenue arrives after it finishes, which is why the replay is a first-class surface rather than an archive.
Embed domains are registered per merchant, so the embed runs where the merchant said it should and not on a page that copied the snippet.
Every step between wanting something and owning it costs conversions, and a live show is the most perishable intent in commerce — the pitch is happening now, the offer ends when the host moves on. Sending that viewer to a product page in a new tab is where live selling on social platforms loses its own advantage.
Cart, orders and the handoff to fulfilment run through the same flow.
Multi-host shows — a second presenter, a guest, a brand collaboration — are available on the higher tiers.
Catalogs import by CSV or from an existing store on the higher tiers, because retyping a catalogue is where a trial ends.
Plans are read from the database rather than fixed in code. As shipped:
The arithmetic is worth doing before choosing a tier: the tier that costs more monthly is the cheaper one above a certain volume of live sales.
Instant payouts are available on the higher tiers, at a pass-through cost — stated as a pass-through because it is the payment network's fee rather than a margin.
Cash-flow timing is a real consideration for a brand running frequent shows: inventory bought for Thursday's show is paid for before Thursday.
Instant payouts are available on the higher tiers, at a pass-through cost — stated as a pass-through because it is the payment network's fee rather than a margin.
Cash-flow timing is a real consideration for a brand running frequent shows: inventory bought for Thursday's show is paid for before Thursday.
The deeper layer on the higher tiers adds engagement heatmaps showing where attention held and where it dropped, and cohort views separating a first-time viewer from a returning one.
The metric that matters commercially is live-driven attribution: which revenue came from the live layer rather than from ordinary store traffic. It is what the commission is charged against, so it is stated rather than estimated.
It reads the merchant's own show data. It does not generate products, prices or claims.
The deeper layer on the higher tiers adds engagement heatmaps showing where attention held and where it dropped, and cohort views separating a first-time viewer from a returning one.
The metric that matters commercially is live-driven attribution: which revenue came from the live layer rather than from ordinary store traffic. It is what the commission is charged against, so it is stated rather than estimated.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Mux
Freshsales
Pipedrive
Pabbly Connect
AWS S3Hover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 55 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 62 tables, as text
active_boosts · admin_notifications · announcement_dismissals · announcements · api_key_logs · api_keys · audit_logs · automation_log · automation_templates · cart_items · carts · catalog_products · chat_messages · credit_balances · credit_transactions · currencies · data_exports · data_imports · embed_domains · faq_categories · faq_items · feature_flags · inbound_webhooks · languages · live_shows · notification_log · notification_rules · notifications · order_items · orders · organization_limit_overrides · organizations · payout_accounts · payout_transactions · plans · platform_secrets · platform_settings · product_purchases · product_variants · products · provider_prices · push_devices · reactions · report_templates · roles · scheduled_tasks · show_analytics · show_analytics_snapshots · show_product_events · show_products · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · video_product_timestamps · viewer_sessions · vod_videos · webhook_logs · webhooks
The chassis, and anything particular to this product. 7 required.
Any Node 18+ host — Vercel, a VPS or Docker. No platform lock-in.
Vercel ↗Postgres with row-level security, applied by the shipped migration scripts.
Supabase ↗A self-hosted OvenMediaEngine VPS carries the live broadcast and LiveKit powers multi-host shows; replays are delivered through Bunny CDN. Keys are wired at /admin/integrations.
OvenMediaEngine ↗LiveKit ↗Bunny CDN ↗Each merchant connects their own Stripe account; sale proceeds land there. The platform charges its commission and never becomes the holder of merchant funds.
Stripe ↗Four adapters ship — bring an API key for any one. Order confirmations, show notifications, account email.
Resend ↗SendGrid ↗Mailgun ↗Brevo ↗Product media lives in Supabase Storage; stream recordings and replay delivery ride Bunny.
Supabase Storage ↗Bunny ↗The embed goes on it. Cartcast does not host a storefront.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 115,901 lines across the application and its database, 62 tables defined by 58 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Cartcast demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 4 of them: Show producer, Merchant owner, Analyst, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 85 page modules and 266 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, OvenMediaEngine + LiveKit (streaming), Stripe, with Connect Express accounts, Email: Resend, SendGrid, Mailgun or Brevo, Supabase Storage + Bunny (object storage), The merchant's own site. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 58 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $249?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.