Branchly
A visual canvas for branching quizzes and forms, with a player as polished as Typeform's — sold once as a multi-tenant SaaS you rebrand.
Branchly is a visual canvas for building branching interactive experiences — quizzes, product finders, guided tours, conversational forms, onboarding flows and assessments.
A described idea arrives as an editable graph, not a blank canvas.
Interactive content dies at the first screen. Someone has the idea — a product finder, an assessment, a lead quiz — and then faces an empty editor with twelve unanswered questions about structure. The project moves to next quarter, and next quarter it moves again. Agencies feel this as unbillable setup hours; in-house teams feel it as a backlog item that never reaches the top. The cost is not a bad experience shipped, it is the good one that never got built because starting it was the expensive part.
- AI experience generation
- Template gallery + clone
You learn which branch loses people, not only that some were lost.
A completion rate on a branching experience answers almost nothing. Two paths through the same quiz can perform completely differently, and an aggregate number averages them into a figure that describes neither. Teams end up guessing at which question is doing the damage, rewriting the wrong screen, and watching the number fail to move. The work of improving the experience becomes a sequence of coin flips, and after a few of them people stop trying to improve it at all.
- Funnel + per-path analytics
- Basic analytics (completion, totals)
The experience lives inside the customer's site, under their brand.
An interactive experience that requires sending people somewhere else loses most of them in the handoff. A link to an external tool reads as a third party asking for attention, and the branded page it lands on is not the one the visitor chose to be on. For an agency the problem is sharper still: the client is paying for something that will sit on their own site, and a visible vendor frame around it is the difference between a deliverable and a demo.
- White-label embed
Every tier reports completions and totals.
That per-path view is the payoff of building on a canvas. A linear form reports only that people left at question seven; a graph reports that everyone who chose one branch finished and everyone who chose the other did not.
Numbers are pre-aggregated as responses arrive, so a busy experience reports on complete data rather than a truncated sample. Nothing is silently cut off — a count that quietly stops at a limit is worse than no count.
Responses export as CSV from the first paid tier.
Two checks stand between generation and a published experience:
When the model cannot produce a valid structure it says so instead of returning something plausible-looking. An invalid graph in a generator's output is a half-finished quiz shown to a real visitor.
Generation is metered per month, with a small allowance on the free tier.
Every tier reports completions and totals.
That per-path view is the payoff of building on a canvas. A linear form reports only that people left at question seven; a graph reports that everyone who chose one branch finished and everyone who chose the other did not.
Numbers are pre-aggregated as responses arrive, so a busy experience reports on complete data rather than a truncated sample. Nothing is silently cut off — a count that quietly stops at a limit is worse than no count.
Responses export as CSV from the first paid tier.
Every tier reports completions and totals.
That per-path view is the payoff of building on a canvas. A linear form reports only that people left at question seven; a graph reports that everyone who chose one branch finished and everyone who chose the other did not.
Numbers are pre-aggregated as responses arrive, so a busy experience reports on complete data rather than a truncated sample. Nothing is silently cut off — a count that quietly stops at a limit is worse than no count.
Responses export as CSV from the first paid tier.
Four trigger modes: on click, after a timer, at a scroll depth, or on exit intent. The frame resizes itself to the content and reports completion and dismissal back to the host page.
Custom domains are available on the higher tiers, and removing the player's branding is available from the first paid tier — with full white-label embedding on the agency tier.
Score and variables together are what make branching expressive: a route can depend on an explicit answer ("they said acne"), on an accumulated total ("they scored under 4"), or on both. Outcomes are then selected by condition, with a final fallback so no respondent ever reaches a dead end.
They are full working graphs, not empty shells with a title. A gallery of blank templates teaches a new builder nothing about what the tool can do, which is exactly why these carry real questions, real branching and real outcomes.
Available on every tier.
Plans are read from the database rather than fixed in code. As shipped:
That is what makes the format work as a top-of-funnel asset: a quiz that requires signing up first is a quiz nobody finishes.
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
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover 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 43 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 51 tables, as text
active_boosts · admin_notifications · ai_generation_usage · announcement_dismissals · announcements · api_key_logs · api_keys · audit_logs · automation_log · automation_templates · credit_balances · credit_transactions · currencies · data_exports · data_imports · experience_analytics_rollup · experience_responses · experience_sessions · experience_templates · experiences · faq_categories · faq_items · feature_flags · inbound_webhooks · languages · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · product_purchases · products · provider_prices · push_devices · report_templates · response_events · roles · scheduled_tasks · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · usage_periods · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 3 required, 2 optional.
No platform lock-in.
Postgres with row-level security, applied by the shipped migration scripts.
Only the prompt-to-experience feature depends on it. Building by hand, publishing, embedding and analytics all work without it.
Configured by the operator, not hardwired.
Account and notification email.
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 — 117,328 lines across the application and its database, 51 tables defined by 63 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 Branchly 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: Creator, Workspace owner, Viewer, 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. 73 page modules and 232 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, An AI provider key, A payment provider, Email provider. 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 63 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.