About Ripllo

Ripllo is the marketing and retention layer of the Forjio family. Discounts, referrals, abandoned-cart recovery, pixels, product feeds, and a storefront blog — one bounded service that plugs into your Storlaunch storefront in a click.

We extracted Ripllo out of Storlaunch in 2026 because growth tooling had grown too big to live inside the storefront monolith. Discount codes, referral programs, server-side CAPI dedup, and Google Merchant feeds each deserved their own surface — and their own release cadence.

Now Ripllo runs as its own service with its own database, its own CLI, and its own portal. Storlaunch consumes it through the same Pattern 2 partner-billing model that Plugipay and Fulkruma use, so merchants still see one bill, one login, one experience.

Our principles

• Marketing as a bounded service. Discounts, referrals, abandoned cart, pixels, feeds, blog. One tool, one mental model. Not an everything-suite that does each thing badly.
• Server-side first. CAPI dedup with event_id, server-rendered Meta Pixel, properly attributed referrals. Browser-only pixels are an anti-pattern we're not perpetuating.
• One identity, one bill. Sign in via Huudis. Settle via Plugipay. When you turn on Ripllo from a Storlaunch storefront, it rolls into the same Storlaunch invoice — no separate billing relationship to manage.
• CLI and API parity. Every dashboard surface is also a CLI command and a REST endpoint. Marketing automation should be scriptable.

Built by Forjio

Ripllo is built and maintained by the Forjio team alongside Huudis (auth), Plugipay (payments), Storlaunch (storefront), and Fulkruma (stock & shipping). One platform, six bounded services, growing.

Questions? Reach us at support@forjio.com.