Documentation/Resources/Contact & Links

Contact & Links

Where to reach the Supero team, where the product lives, and where to follow along.

Contact

Pick the address that matches what you need — it reaches the right people faster than a general enquiry.

Address	Use it for
[email protected]	General enquiries, partnerships, press, and anything that does not fit below.
[email protected]	Something is broken, erroring, or behaving differently from these docs.
[email protected]	Production launches, custom domains, capacity planning, and deployments into your own AWS/GCP or on-premise.
[email protected]	Vulnerability disclosure. Please mail here before opening anything public.

💡 Getting a faster answer on support

Include your domain name, the project, the exact endpoint or screen, the timestamp, and the full error body. Most support round-trips are spent establishing those five things.

⚠️ Security reports

Please do not file a vulnerability as a public issue or a social post first. Mail [email protected] and we will acknowledge and agree a disclosure timeline with you.

Ask the Community

Questions about building on Supero, and the apps people have built with it, go in GitHub Discussions on the supero-apps repo. Answers there are public, so the next person with the same question finds them, and the Supero team reads every thread.

Category	Use it for
Q&A	How do I…? Something in these docs is unclear. A schema, role or workflow that is not behaving the way you expected.
Show and tell	An app you built on Supero. Link the live URL and the source if it is public.
Ideas	A feature, a missing integration, or a reference app you would like to see.

ℹ️ Private or account-specific?

Anything involving your account, billing or private data goes to [email protected] instead, and security reports always go to [email protected], never to a public thread.

Where Things Live

Supero is several hosts, and it helps to know which one you are talking to when something misbehaves.

Host	What it is
supero.dev	The marketing site — product overview, sample apps, and solutions.
app.supero.dev	The dashboard. Sign up, build in App Studio, manage projects, tenants, and deployments.
api.supero.dev	The REST API every SDK, CLI, and integration calls. Base for all `/api/v1/...` paths in these docs.
docs.supero.dev	This documentation.
`*.supero.live`	Where deployed applications run. Each published app gets its own subdomain.

ℹ️ Which host does an error belong to?

An error while building or managing belongs to app.supero.dev. An error from a curl or SDK call belongs to api.supero.dev. An error your end users see belongs to your app on supero.live. Naming the host in a support mail usually halves the triage time.

Follow & Sample Code

Supero on LinkedIn

Product updates, engineering write-ups, and release notes. linkedin.com/company/supero-dev

Supero on X

Release notes, build-in-public threads, and the occasional teardown. x.com/SuperoDev

GitHub

supero-platform/supero-apps

Sample applications you can read, clone, and run. github.com/supero-platform/supero-apps

Demo

Watch a build end-to-end

From a plain-language description to a deployed application. Watch the demo

Gallery

Sample apps

Applications built on Supero, running live. supero.dev/apps

Before You Write In

A surprising share of questions are already answered in one of these four places. They are worth a minute before you open a ticket.

Quick Start

Domain, project, schema, first CRUD call. Read it

Core Concepts

What a domain, project, and tenant actually are. Read it

Solutions

Ten reference architectures with build paths. Browse them

API Overview

Conventions, auth headers, and error shapes. Read it

← PreviousA Subscription Business, End to End Next →Architecture

On this page