Unlock revenue through
widgets
Sell more to the customers you already have and get in front of the users other startups have.
Widget integrations between SaaS products
A widget integration is one feature of your product, packaged so another product can embed it. Their users get your feature without leaving the product they already use, and sign up and pay for it inside the widget. On Ordana you set the price, the free uses and the share the host keeps before anyone integrates, and every sale is split automatically.
How a widget gets you new users
1. Set it up
Build your widget on Ordana.
Your coding agent builds it with you. Ordana runs the sign-up and checkout inside it.
2. Your page
Get your own widget page.
One link any founder can open to add your widget to their product.
3. Sell it yourself
Then go out and sell it.
Send your link to the founders whose users you want. Every product that adds it brings you its users.
4. We help
We list it, too.
Ordana's directory and matching send extra founders your way.
5. Get paid
Every sale pays you.
Ordana takes the payment and splits off the host's share. The rest is yours.
List your SaaS as a widget · Add a widget to your product · How it works
Widget integrations, explained
How to build an embeddable widget, embed one in your product, price it, and get other products to add yours.
- GuideWhat Is a Widget Integration?A widget integration is one feature of your product, packaged so another product can drop it in. Their users get your feature without leaving. That's the door.Read the guide
- GuideHow to Embed a Third-Party Widget in Your SaaSIframe or script tag, card, page or modal, how it sizes itself, how it matches your design, and who signs the user in and charges them. The host-side checklist for embedding a widget.Read the guide
- GuideHow to Create an Embeddable Widget for Your SaaSOne feature, one iframe, built to live inside someone else's product: how to size it, theme it, sign users in, meter free use and ship a preview a host can actually open.Read the guide
- GuideWidget vs API Integration: Which Should Your SaaS Offer?An API asks every partner to build your feature again. A widget asks them to place it. When each one wins, and why the products that get integrated most offer both.Read the guide
- GuideHow to Price an Embeddable Widget: 5 Models ComparedYour widget lives inside someone else's product, in front of users who never chose you. Free with a cap, subscription, credit packs, both, or pay per use: when each fits, and what the host should keep.Read the guide
- PlaybookHow to Get Other SaaS Products to Integrate YoursMost integration requests die because the host does the work, takes the support and gets nothing. Offer a finished widget with the terms set first, ask the right products, and ask with one link.Read the guide
Frequently Asked Questions
What is Ordana?
Ordana is a free directory of widget integrations between SaaS products. A startup lists one feature of its product as a widget; any other startup can embed it in its own product, where its users sign up and pay inside the widget, and every sale is split between the two automatically. Ordana also runs revenue-share collaborations end to end: the matching, the plan, the contract, the tracking and the payouts. The members write the integration code themselves, with their own coding agent, from a prompt Ordana writes.
What is a widget integration?
A widget integration is one feature of a SaaS product packaged so another product can embed it. The host's users get the feature without leaving the product they already use, and sign up and pay for it inside the widget. On Ordana the terms (the price, the free uses and the share the host keeps) are set before anyone integrates, and every sale is split automatically.
What is a widget on Ordana?
One capability of your product, packaged in two parts. The embed: a view another product places as a card inside one of its screens, as its own full page, or in a modal opened from its own button. It takes the host's colours and fonts, but the host can't restyle what's inside it. The integration package: how sign-in works, which calls a host may use, and how much notice comes before a breaking change. Users sign in and pay inside the widget. Any startup on Ordana can add a listed widget with no application and no approval.
How do I add a widget to my product?
Open the widget's page on Ordana and press Add. You get one prompt to paste into your own coding agent: it asks you a few questions, builds the embed into your product, and returns a short report you paste back, and the widget goes live. It can sit as a card inside one of your screens, as its own full page, or in a modal opened from your own button, and it takes your colours and fonts. No application, no approval, and Ordana never reads your repository.
How do I list my startup on Ordana?
Sign up free with your website, then create your widget: Ordana gives you one prompt to paste into your own coding agent (Claude Code, Codex, Cursor or similar). It asks you about eight questions, each with its own recommendation, builds a clickable preview in your own codebase and returns one block of JSON you paste back. Confirm your price, your free uses and the share a host keeps, and press List. You get a public widget page any founder can add it from, and an "Add to your product" badge for your site. Ordana never reads your repository.
Should my SaaS offer a widget or an API integration?
An API suits a partner with engineers who want their own interface and to sync data both ways. A widget suits a partner who wants the feature working this week: you build the interface, sign-in and checkout once, and every product that adds it embeds the same thing. Plenty of products should offer both, which is why a widget on Ordana carries its API documentation alongside the embed.
How do widget sales get paid out?
Ordana is the merchant of record for widget sales. The user pays inside the widget, and Ordana pays the host its share and the widget's owner the rest, automatically, through Stripe. The owner sets what the host keeps (10–90%), and Ordana's 10% fee comes out of the owner's share, never the host's. A host with its own accounts and checkout can instead bill its users itself and buy seats from Ordana at the price less its share.
Can my users try a widget for free?
If the widget's owner offers free uses, yes, up to the limits the owner sets, including a cap per host so an expensive feature, like an AI call, can't run up an unlimited bill. After that the user signs up and pays inside the widget, and it updates in place without a reload. Every change to an offer comes with 30 days' notice to the products already using it.
How is Ordana different from Product Hunt or BetaList?
Product Hunt and BetaList are launch directories: a spike of early adopters on launch day, then the list moves on. Ordana is a standing directory of SaaS widgets, where the people finding you are founders looking for a capability to build into their own product — so a listing turns into integration partners rather than upvotes. Most startups should do both.
Is Ordana free to use?
Yes. Listing your startup, creating your widget and adding anyone else's are free, and so is joining. On revenue-share collaborations Ordana charges a flat 10% platform fee only when revenue actually flows through one — so you only pay when you're making money. On widgets, Ordana only earns when one sells: its fee comes out of the widget owner's share, never the host's.
Who is Ordana for?
People who build software products: SaaS companies, web apps, mobile apps, developer tools, AI products, marketplaces — early-stage and bootstrapped first. "Are you SaaS?" is actually the wrong question, though. The one that predicts whether this works is: do you hold something your users generated that they can't act on inside your product? A client roster, usage signal, a request history, a saved library. That's what a partner can plug into and act on — and you need a surface for them to do it through: an app UI, an API, an AI or agent surface, or control over your own checkout. It also works for agencies, creators and service businesses, who run the same play commercially rather than technically — folding a partner's offer into their own engagement instead of integrating code.
What is an integration partnership?
An agreement between two software companies to build into each other's products, so a customer they share can finish more of their job without leaving either app. The technical half is the integration, and it's the half everybody writes about. The commercial half — who gets paid what, by whom, for how long — is the half that decides whether it's still working next year, and it's usually missing entirely: referral partners typically earn 10–20% of first-year revenue and resellers 20–40% of ongoing revenue, while integration partners normally get a launch post. An integration nobody is paid for is an integration nobody maintains. Ordana structures the other kind, where the integration itself is the revenue source.
What is a scenario collaboration?
A scenario is a standing, reciprocal cross-sell relationship between three or more complementary products. Each member keeps their own users and their own revenue, and any member's user can pull in the others — so every member's growth feeds the rest. The defining trait is multiple revenue streams: two or more members each bringing their own revenue, shared across the group. When the members are software, they pool those users by integrating into each other's apps, so the shared user experiences one suite instead of five subscriptions.
Do I have to build the integration myself?
Yes — today that part is yours. Ordana finds the partners, designs the integration plan, and handles the contract, revenue tracking and payouts. The code ships in your own codebase, on your own schedule, and we never ask for repo access. We'd rather tell you that up front than promise automation that doesn't exist yet.
Isn't this just an affiliate link?
No, and being paid per transaction isn't what makes something an affiliate network. Two other things do: it's one-time (a bounty on a signup ends the relationship at the handoff, and neither side cares what happens next) and it's one-directional (value only ever flows one way). A perpetual share of an account's lifetime makes both sides care whether that customer stays, and because every member is both host and partner, it runs in both directions. There's also a simpler difference: an affiliate link moves a lead, while an integration changes what you can sell — your users can do something inside your app they couldn't do before, and you charge for it.
Who fixes it when the integration breaks?
Whoever's product the user is looking at takes the first-line support — it's your UI, your customer, and they shouldn't have to work out whose fault it is. The partner owns the thing underneath and commits to a response time in the plan, so an outage has an owner and a clock before anything goes live rather than becoming a founder-to-founder argument afterwards.
Do I have to share all my revenue?
No. You choose exactly which products or prices are in scope when the revenue-share rule is set up, and everything else is untouched. Most members share the add-on or plan the integration actually created, not their whole business.
I only have a few hundred users — is this worth it?
This isn't a traffic play, so a small user base doesn't disqualify you. You don't need more visitors; you need more to sell to the ones you already have. A few hundred engaged users who suddenly have three more things worth buying is a bigger revenue change than a spike in signups — and it doesn't cost anything to try.
How does revenue sharing work?
You define the terms together — what percentage goes to each party, for how long, and with what cap. Once everyone signs, Ordana automates the payouts: when revenue lands in a member's connected Stripe account, the agreed share is transferred to the others. Each member keeps their own Stripe account and their own pricing; money is never pooled.
How do I know I can trust my collaborators?
Ordana builds trust into the infrastructure. Every collaboration has a clear contract, defined deliverables with acceptance criteria, and built-in dispute resolution. Signatures are identity-verified, and completion history and peer evaluations are tracked, so you can see a collaborator's track record before you commit.
What if I already know someone I want to collaborate with?
Invite them directly and set the collaboration up together. You get the same infrastructure — plan, contract, revenue splits and automatic payouts — even if you found each other outside the platform. Plenty of integration deals stall because nobody wants to draft the agreement; that's the part Ordana removes.
Can this help me get clients for my agency?
Yes. List what you offer, get matched with businesses that need your expertise, and structure deals on revenue share. You can also join a scenario with complementary providers so a single engagement covers more of what the client needs — a bigger scope you can charge more for, with the split handled behind the scenes.
What happens when I upload my LinkedIn connections?
They become a private search index only you can use. Tell Ordana's AI what you're trying to achieve and it designs a collaboration, then searches your own network for the people who can fill each role — so you can start with a warm intro instead of a cold email. Your connections stay private to you: Ordana never contacts them, never shows them to other users, and never stores your raw export file — only names, companies and roles. You can delete them all at any time.
Free to list. Pay only when revenue flows.