Skip to content

Platform

Find capabilities by business goal

Every capability below is running in production. Each section describes the problem it addresses and the benefits it delivers; technical details are available on request.

Web container SDK Live

Native-quality web pages inside your app

The challenge

Delivering app features as web pages improves development efficiency, but the user experience often suffers: blank screens, slow loading, no access to native capabilities, and inconsistent behavior between Android and iOS.

How SuperPlatform addresses it

SuperSDK provides a pre-configured web container: page assets ship with the app for instant loading, web code calls login, payments, sharing, files and ads through a unified interface, and both platforms behave identically.

Benefits

  • One web codebase serves Android and iOS, with graceful degradation in a browser
  • Offline bundles load instantly and are generated automatically when a site is published
  • Dozens of native capabilities available directly; microphone and file-picker permissions handled by the container
  • Login, payments and ads available as optional modules
Technical details
  • Android is distributed via Maven (com.supersdk:supersdk, minSdk 23); iOS via SPM / xcframework (iOS 14+).
  • Web code calls native through window.appbridge, wrapped as SuperSDK.*; both native implementations are generated from a single protocol manifest.
  • Offline bundles are matched by host@version; Android intercepts per request, iOS uses request-level interception with SPA fallback.

SuperCLI and project templates Live

From template to production in one command

The challenge

Starting a new project requires scaffolding multiple codebases, configuring numerous scripts, and mastering the build and release process of each platform.

How SuperPlatform addresses it

SuperCLI describes the entire workspace in a single configuration file: pulling templates, building all targets, publishing sites and services, reading logs, querying data and changing configuration are all performed through commands. Existing projects can be registered directly.

Benefits

  • Android / iOS / web / backend templates pulled in one command and ready to run after renaming
  • All targets built in a single pass, with artifacts archived together
  • One login manages multiple accounts and environments; CI runs unattended with an API token
  • Every command provides machine-readable output for AI assistants and automation
Technical details
  • npm package @supersdk/supercli, Node.js 18+; the workspace configuration is super.json (schemaVersion 5).
  • With --output json, stdout is exactly one JSON line with stable exit codes; set SUPERCLI_TOKEN to an sst_ API token for unattended runs.
  • Site deployments are accepted asynchronously; the CLI waits for edge_ready before reporting success.

SuperSite hosting Live

Publish websites without provisioning servers

The challenge

Even a landing page or campaign page requires provisioning a server, configuring a domain, obtaining a certificate and deploying a web server.

How SuperPlatform addresses it

Create a site in the console to receive a subdomain, then publish by upload or command. All reads are served by a global edge network, with version rollback and custom domain support.

Benefits

  • An HTTPS domain upon creation, reachable worldwide within seconds
  • Every deployment retained as a version, with one-click rollback
  • Sites isolated per environment; test and production publish independently
  • The app offline bundle generated automatically on publish
Technical details
  • Site domains take the form {slug}-{spid}-site.supersdk.site (non-production environments are prefixed); computed at runtime, never stored.
  • The read path runs entirely on the Cloudflare edge (Worker + R2) with no origin egress; deployment state is derived from six statuses and edge probing is triggered on read.
  • Custom domains use unified TXT ownership verification with on-demand certificates.

SuperRun hosting Live

Run backend services from a Dockerfile

The challenge

Once the API is written, deployment often becomes the bottleneck: selecting a cloud provider, configuring a cluster, opening ports and locating logs each carry a learning cost.

How SuperPlatform addresses it

Push the image with a single local command and the platform runs it: domain and HTTPS assignment, traffic-based autoscaling, and scale to zero when idle. Logs are available in real time; deploy again after each code change.

Benefits

  • Provide a Dockerfile and receive a domain and a log stream; the platform handles the rest
  • Adjustable replicas and instance size; automatic scale-to-zero incurs no cost when idle
  • A private image registry for every project
  • Custom domains and connections to your own database
Technical details
  • Built on Knative Serving; user containers run in a separate cluster physically isolated from the platform.
  • Images are pushed to the project registry at repo.supersdk.com; service domains are {slug}-{spid}.supersdk.site.
  • Logs are archived by ingest time and can be scanned or followed live from the console and the CLI.

Remote configuration Live

Adjust your app without a release

The challenge

Changing a line of copy or enabling a campaign switch requires waiting for the next release and store review.

How SuperPlatform addresses it

Host these values in the console and fetch them at app startup. Each configuration item can be a script that returns different results by user or version; all changes are recorded with preview and rollback support.

Benefits

  • Immediate effect, no release required
  • Test and production environments managed separately
  • Every change can be compared and rolled back
  • Conditional values for gradual rollouts and audience targeting
Technical details
  • Each item is a JS script executed in a server-side sandbox, a superset of key-value configuration; online debugging and preview URLs are built in.
  • Isolated per project × environment; the SDK falls back from local cache to bundled defaults to remote fetch.

Analytics Live

Clear insight into user behavior

The challenge

Obtaining data requires instrumentation, storage and reporting. Smaller teams rarely have the capacity to build a complete analytics system.

How SuperPlatform addresses it

The SDK includes event reporting, and data is written automatically to a warehouse dedicated to the project. The console presents event trends, retention and custom dashboards; deeper analysis can be performed through read-only queries from the CLI.

Benefits

  • Event trends, retention and dashboards available immediately
  • Isolated per environment so test data does not affect production
  • Queries available from the CLI and to AI assistants
  • Every query recorded and governed
Technical details
  • Events flow through the platform collection pipeline into BigQuery: one dataset per environment, one table per project, partitioned by day.
  • CLI queries are read-only with a mandatory date range and scan limits; executions are recorded and visible in the console.

Attribution · short links · webhooks Live

Accurate insight into user acquisition

The challenge

With many channels and share links, it is difficult to determine which channel actually produced installs and conversions.

How SuperPlatform addresses it

A short link is generated at share time and installs are matched to their source automatically. Attribution results are immutable and delivered reliably to your backend.

Benefits

  • Share links generated with one line of code
  • Installs and activations attributed to channels automatically
  • Results delivered reliably via webhooks
  • Every attribution record available in the console
Technical details
  • Short link domain s.supersdk.com, with support for alias domains.
  • Project-level channels with deterministic project × environment matching; decisions are immutable; multiple webhooks per environment with automatic retries.

SuperDB Live

Connect your existing database

The challenge

Connection details are scattered across systems, and AI assistants that need data still depend on manual exports.

How SuperPlatform addresses it

Register your existing PostgreSQL or MySQL connection with the platform. Credentials are encrypted, connections are verified on creation, the CLI and AI assistants query through a governed channel, and deployed services receive the connection automatically.

Benefits

  • Retain your database; the platform manages the connection
  • Credentials encrypted centrally rather than stored in configuration files
  • Read-only queries are governed; write operations require human confirmation
  • Connection details injected into SuperRun services
Technical details
  • Connections are environment-level entities with envelope-encrypted credentials.
  • Queries run in a read-only transaction with single-statement parsing and row/time limits, fully audited; execute requires explicit confirmation.

SuperScheduler Live

Scheduled execution

The challenge

Periodic tasks such as daily settlement or hourly synchronization should not require a dedicated host running cron.

How SuperPlatform addresses it

Create a scheduled job in the console or the CLI, and the platform calls the specified endpoint on schedule. Signing, retries, pausing and immediate execution are supported.

Benefits

  • Intervals down to one minute, with time zone support
  • Signed requests that the endpoint can verify
  • Automatic retries and pausing at any time
  • Every execution recorded
Technical details
  • unix-cron expressions with time zones; optional HMAC signature header; sensitive headers are sourced only from environment variables.
  • Up to 20 jobs per environment during the beta.

Monetization Live

Login, payments and ads integrated once

The challenge

Google Sign-In, in-app purchases and ad placements each require a separate SDK and involve significant platform differences.

How SuperPlatform addresses it

SuperSDK exposes them as capabilities that web code can call directly: the web page initiates, native completes, and the result is returned to the page. The server only needs to process receipts.

Benefits

  • Purchases and logins initiated with one line of web code
  • Subscriptions and offers queried on demand
  • Rewarded and interstitial ads behave consistently on both platforms
  • Receipts delivered from native directly to your server; the web page never handles sensitive data
Technical details
  • Google Play Billing, Google Sign-In and AdMob ship as optional packages; nothing is bundled unless added.
  • Payments follow createOrder → pay → three-state callback; the server is the source of truth for fulfillment.

User feedback Live

Structured user feedback collection

The challenge

Users lack a clear feedback channel, and comments are scattered across store reviews and support conversations, making systematic follow-up difficult.

How SuperPlatform addresses it

All three platforms submit feedback through one API with version, device and environment attached automatically. The console supports filtering by scene and tracking resolution status.

Benefits

  • Feedback collection integrated in one line of code
  • Device and version details attached automatically
  • Filter, resolve and reopen in the console
  • Isolated per project × environment
Technical details
  • The public intake endpoint is rate limited; field rules are defined on the server and mirrored in the SDKs.

Console · organizations and environments Live

Built for team collaboration

The challenge

As a project moves from individual development to team collaboration, managing accounts, permissions and environments becomes considerably more complex.

How SuperPlatform addresses it

The console manages projects and members per organization, with in-app invitations. Every project includes a production environment and can add test and staging environments; all assets are isolated per environment.

Benefits

  • Sign in with email or a Google account
  • In-app invitations accepted in one click
  • Configuration, sites, services and data isolated per project × environment
  • API tokens for CI and AI assistants
Technical details
  • Up to 100 projects per organization and 5 environments per project during the beta.
  • Roles are admin / member; the scope of API tokens (sst_) and CLI credentials (cli_) is defined by the server-side route policy table.

Roadmap

The following capabilities are in development and will be published here upon release.

  • Beta A/B experiments: deterministic bucketing that records exposure only when a user actually sees the variant
  • Beta Usage and billing: managed through quotas during the beta