Technology Platform

The operating system behind a shared power bank network.

CoreCharge brings compatible devices, rental workflows, supported payment integrations and an operator dashboard together. Start on a shared platform while your team focuses on local venues and service.

Talk About My Architecture Back To Homepage Developer Center

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 with the platform. Choose your next step as you grow.

An independent software project is not a prerequisite for testing local demand. Start with SaaS; brand customization and private deployment are optional projects with separately agreed scope and fees.

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

Consider a dedicated deployment when your business needs it. Confirm migration scope, responsibilities, fees and the implementation plan for your project.

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

Review reported connectivity, slot inventory, rental/return events and supported remote diagnostics. Status depends on device reporting; automatic email/push offline alerts are not included in the standard service.

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.

Marketplace

Catalog, coupons, local marketplace orders and customer retention.

Ride-hailing

Map dispatch, route orders, driver partners and in-app payment.

Food ordering

Restaurant menus, delivery orders, pickup flow and settlement.

Membership

User tiers, points, wallet, coupons and repeat-use campaigns.

Advertising

Screen campaigns, venue promotions, content scheduling and data.

Merchant services

Merchant tools, POS, settlement, support tickets and local services.

Daily operations and your next software step

Know what the standard dashboard shows, what remains an operator task and how a future integration is handled.

What can the dashboard tell me about a station?

With the appropriate permissions, review reported station/slot status, inventory, orders, payment references and status, pricing and revenue. Supported actions can include remote diagnostics and equipment control. These are reported states, not an independent inspection of every physical fault. Automatic email/push offline alerts are not currently included in the standard service.

Can staff export reports and manage venue commissions?

Available Excel exports and venue/device-level order and revenue views follow your account roles and menus. Supported commission calculations can be configured; reports do not automatically transfer money to venues. CSV can be prepared from exported spreadsheets. Confirm the actual fields and roles in your account demonstration; arbitrary custom metrics and permissions are not standard features.

Can my purchased hardware later use my own backend?

Yes, after the necessary compatible development and integration. CoreCharge does not charge a hardware migration or firmware-unlock fee or impose a punitive hardware lock for leaving the hosted platform. Device communication information and necessary integration guidance are provided; this does not include free custom development or ownership of CoreCharge source code. Separate signed commitments still apply.

Plan the right architecture before the first shipment.

Tell us your country, payment method, expected station count and whether you want SaaS trial, own-brand upgrade or private deployment.

WhatsApp sales@corechargecloud.com

Content reviewed: 20 October 2026