Opera Source Code Join the list
How it works

From purchase to a published app

No server to set up and no manual to follow. The installer does the heavy lifting.

  1. Pick a product

    Try the demo, see the screenshots and what’s in the package. Regular or extended license.

  2. Run one command

    The installer asks for your license, signs in to your Cloudflare account and asks for your Opera keys. It does the rest.

  3. Adjust in the admin

    Color, style, corners, font, sign-in methods and languages. The app changes without shipping a new version.

Why it’s different

What almost every template promises and doesn’t deliver

Installs with one command

No 40-page manual. The installer creates the database and storage, publishes the API and admin, and generates the configured app.

All on your Cloudflare

No server to maintain. API on Workers, D1 database, files on R2. It runs on your account, under your name.

A real demo

Every product has a public demo, published by the same command you will run. What you see is what you get.

React Native and native

A React Native app for Android and iPhone and, where it makes sense, a native version in Kotlin and Swift.

Four languages, Arabic included

Portuguese, Spanish, English and right-to-left Arabic on every screen, in the app and in the admin.

Voice, video and chat built in

Calls, voice rooms and live streams through Opera Signal, with SDKs for the app and for your server.

Sign-in

However your customers want to sign in

Every product uses the same sign-in base. You turn each method on and off in the admin, choose the order and the main one, and a user signs in to all of your products with one account.

  • Email code
  • Email and password
  • SMS
  • WhatsApp
  • Google
  • Apple
  • Facebook
  • Magic link
  • Guest