Chuhai Cloud
Operated by 1583523 B.C. LTD. · 788 Beatty Street, Vancouver, British Columbia V6B 2M1, Canada

Home / Product

What is inside Chuhai Cloud

Chuhai Cloud is one web application with two halves. Social operations is where a team prepares content, publishes it to the accounts they own, and reads the numbers back. Customer management is where the messages, comments and enquiries those posts produce are answered and tracked. Both halves work only on accounts the customer has connected through the platform's own consent screen.

Publishing

Prepare a post once, choose which connected accounts it goes to, publish or schedule it, then track what happened on a board.

Inbox & comments

Direct messages and comments from every connected account in one queue, with inline translation and reply.

Analytics

Followers, views, likes and posts for the accounts a company owns, by account, by country and over time.

Google Ads

Spend and performance from the customer's own Google Ads account, plus pause and resume for campaigns in it.

Account matrix

Connected accounts organized by product line, country, language and the teammate responsible for each.

Leads

An enquiry that arrives in the inbox can become a tracked lead with an owner, a stage and a history.

Prefer to just look at it? The product tour walks through all eight screens with a caption on each.

Account matrix

A cross-border seller usually runs more than one account per platform: one per brand, per market, or per language. The account screen is the register of those accounts — which platform each one is on, which product line and country it serves, which teammate owns it, and the follower and view counts last read back from the platform.

Accounts appear here only after their owner has completed the platform's OAuth consent screen inside Chuhai Cloud. Disconnecting an account here deletes the stored tokens for it.

Account matrix screen listing connected TikTok, YouTube, Instagram and Facebook accounts with platform, market, owner and follower counts.
Account matrix. Each row is one account the customer owns and has connected.

Leads

When a conversation in the inbox turns into a real enquiry, it can be promoted to a lead: an owner, a stage, tags, and the message history that produced it. This exists because the people running these accounts are a sales team, not a content team — the point of the post is the enquiry it produces.

Lead records are the customer's own business data. They are stored in that customer's workspace only, and are covered by the same retention and deletion rules as everything else (see Security and data handling).

Lead pool screen showing enquiries with owner, stage, source platform, country and last activity.
The lead pool. Enquiries carry the platform and account they came from.

How the application is built

Front end

React 19 with TypeScript, built with Vite, styled with Tailwind. Routes are code-split, so opening a screen loads only that screen.

Back end

A Python service (FastAPI) with a per-tenant database. All browser traffic goes through one gateway contract, and every call carries the signed-in user's token.

Platform adapters

Each platform integration is a separate adapter, so a change in one platform's API cannot break another. Adapters call official endpoints only.

Hosting

The application runs on servers in Hong Kong and is available to businesses in markets where the connected platforms operate. It is served over HTTPS only.

Next