Technology Platform

The operating system behind a shared power bank network.

CoreCharge Cloud connects devices, rental flows, payments, merchants, agents, dashboards and private deployment migration in one SaaS-first architecture.

Talk About My Architecture Back To Homepage

CoreCharge
Cloud

Device Cloud

Rental App / H5

Payment Gateway

Operator Console

Agent & Merchant Roles

API & Private Deployment

System Architecture

A full IoT SaaS map from device access to delivery operations.

The platform is organized around device connection, traffic access, microservice governance, PaaS support, monitoring and CI/CD release, so operators can start with SaaS and later migrate into their own deployment.

IoT SaaS Platform Architecture

Device access, client traffic, microservice governance, platform support, monitoring and CI/CD delivery loop.

Access & Load Business Services Governance PaaS Support Monitoring

Internet VUE Frontend Micro Frontend SaaS Services

Access Layer

IoT devices connect through TCP long connections, while mobile and web clients access business capabilities through HTTP.

IoT Devices TCP Long Connection

Vending machine Laundry machine Power bank Charging cable Charging pile Hair dryer

Client Apps HTTP Access

Android iOS Mini Program H5 Admin Console Rental UI

Edge Load Layer

F5 hardware load balancing and LBS route TCP / HTTP traffic into the Nginx access cluster.

F5 Hardware Load Balancer LBS Load Balancing Nginx Cluster

Backend Service Cluster

Spring Cloud microservices coordinate registration, configuration, gateway forwarding, authentication, SaaS personalization and business calls.

Service discovery Nacos Registry Register and pull services

Application services Spring Cloud Gateway

User auth center SaaS basic service Payment center Advertising center Device management Admin console Report service Order center External connector Scheduled tasks Workflow Product factory

Configuration governance Nacos Config Center Pull and push configuration

PaaS Service Support MySQL Redis ElasticSearch RocketMQ OSS

Monitoring Center

Monitoring data is reported to support services, then exposed through API, APM, transaction and log query tools.

Service support

API auto scan Log center PinPoint Transaction monitor Prometheus

Web layer

API management APM management Transaction query Log download Grafana

CI/CD Delivery Chain

Code, dependency, build, image, orchestration and operations release steps form a repeatable delivery loop for overseas projects.

Developer commit Gitee Nexus Jenkins Docker Rancher + K8s OPS release

Launch Path

Start light, prove the market, then migrate into ownership.

The platform is designed for B2B operators who want a lower first-test cost before they commit to a full local brand and private system.

SaaS pilot

Start with a small batch of stations and a prepared workspace to test venues, pricing, payment success and rental behavior.

Alliance brand operation

Operate as a local agent or partner under a ready brand while building merchant relationships and operational data.

Own-brand upgrade

When the model works, customize brand identity, app/H5 UI, hardware appearance, pricing rules and payment configuration.

Private deployment

Move devices, merchants, orders and operating rules into your own privately deployed system when the business is ready.

Core Modules

A platform built around real rental operations.

The technology layer is not just a website or app. It supports device events, pricing, settlement, refunds, merchant permissions and data visibility.

Device connection

Online status, slot inventory, rental and return events, fault alerts and remote station configuration.

Order and payment engine

Deposit, pre-authorization, timed billing, refunds, wallets and local payment gateway integration by market.

Roles and settlement

Platform, brand, agent, merchant and store roles with separated data scopes, balances and operating permissions.

Dashboard intelligence

GMV, orders, devices, merchant rankings, activity trends and abnormal station signals for daily operations.

Open API layer

Connect local payment providers, membership systems, websites, apps, merchant tools and later business modules.

Migration base

Preserve devices, merchants and operational logic so the SaaS pilot can grow into a private deployment path.

Microservice Expansion

After charging works, the same architecture can expand.

A proven local rental network can later connect marketplace, ride-hailing, food ordering, membership, advertising, merchant services or other regional business modules.