Skip to main content

​
Overview

If you need to run superun Cloud in your own intranet environment and ensure business data never traverses the public internet, you can opt for private / self-hosted deployment. superun offers two paths.

​
Path 1: Self-hosted deployment (no technical support)

  1. Export the frontend code from the project during the development stage
  2. Deploy the code to your own server or a third-party hosting platform (e.g., Netlify, Vercel)
  3. Backend data, authentication, cloud functions and other capabilities that depend on superun Cloud need to be re-implemented by you
For this path, maintenance, security hardening, upgrades, and troubleshooting of the self-hosted code are entirely your own responsibility. The superun team does not provide deployment-related technical support for self-hosted environments.

​
Path 2: superun enterprise private deployment (paid service)

superun deploys inside the customer’s intranet environment, so app generation and runtime both happen within the network and business data does not traverse the public internet.

​
What gets deployed

In simple terms, superun Cloud is “moved” into your own data center / cloud account. It mainly includes:
  • superun Cloud: provides your business app with APIs, login/authentication, data read/write, and more
  • Database: stores business data and the information needed to run
  • Intranet access entry: lets your app reach superun Cloud over the intranet
  • Management channel: within the scope you authorize, the superun team handles deployment, upgrades, checks, and troubleshooting
Your business app only needs to connect to the superun Cloud address — you don’t need to understand how it runs internally.

​
Choosing between the two deployment methods

Based on your existing infrastructure, superun picks one of the following: Method 1 · Use your existing container platform (recommended, for production) If you already have a Kubernetes cluster (e.g., Alibaba Cloud ACK or Tencent Cloud TKE), both superun Cloud and its database run inside it.
  • Pros: clear isolation, long-term stability, good scalability; when resources are sufficient, you can create multiple projects on demand
  • You provide: setting up and maintaining the cluster, plus storage and backup capability
Method 2 · Provide only servers + a database (for pilots / lightweight deployment) If you don’t have a cluster and only provide a few servers and a database (PostgreSQL/RDS), superun Cloud runs on the servers and data is stored in your database.
  • Pros: lower upfront cost, quick to start
  • You provide: servers, a database, and the intranet network
  • Key limitation: unlike Method 1, this method cannot create new projects at any time — each new project requires a separate database to be prepared first. A validation round (POC) is required before going live.

​
Quick comparison

​
Basic network prerequisites (both methods)

  • Your business app can reach superun Cloud over the intranet
  • The database is not exposed to the public internet by default
  • The runtime environment can access superun’s designated image registry
  • DNS, certificates, load balancing, firewall, etc. are configured on the customer side
Specific server specifications, storage, and network details are provided by the superun technical team during onboarding based on your environment — you don’t need to figure out all the technical parameters in advance.

​
Intranet environments without public internet access

Government, enterprise, or other isolated networks that cannot access the public internet usually require source delivery and manual deployment:
  1. Export the project source code from an environment that can access superun.
  2. Prepare the dependencies and deployment files required to run the source code.
  3. Transfer the files into the intranet through the customer’s approved security process.
  4. Deploy the project on customer-provided servers and databases.
  5. After the project changes, export the source again and update the intranet version manually.
Confirm the following before deployment:
  • Whether the intranet can call external APIs, including AI, SMS, maps, or other third-party services
  • Who maintains the database, file storage, logs, and backups
  • How intranet domains, certificates, and access permissions are configured
  • Whether data residency, audit, security certification, or domestic technology requirements apply
A fully isolated environment cannot directly use automatic deployment or third-party services that depend on the public internet. The customer technical team and superun team must evaluate available capabilities, delivery method, and compliance requirements before deployment.

​
Cost

Enterprise private deployment involves a one-time implementation fee and regular usage fees. Overall, Method 2 has a lower upfront cost but database-related costs grow as projects increase; Method 1 has a higher initial setup cost but scales more comfortably over time. For specific fees and a quote, please contact superun (WeCom customer service or sales). We’ll provide a plan tailored to your environment and chosen deployment method.

​
Getting started

Add our WeCom customer service or contact sales, describe your intranet environment and deployment needs, and the superun team will provide a corresponding technical onboarding plan and quote.