User manual

1Roles & architecture

CaaS moves a network device's console port into the browser: someone on site plugs in a cable, and a remote engineer opens a web page to type commands, paste configs and capture logs — no client, no VPN.

2Field setup

2.1 Open the field console

• Browser: open https://caas.support/phone.html on a phone or laptop.
• Android app (recommended on site, stays online with the screen off): download https://caas.support/caas.apk and install; upgrading keeps your data, and the app checks for updates automatically. Note: the app's invite link is an unencrypted channel — use the web field console for end-to-end encryption.

2.2 Cabling

Phone USB-C → OTG adapter → USB-RS232 adapter (FTDI / CH340 / CP210x are driverless) → rollover cable → device console port. Most devices use RJ45 or DB9.

2.3 Serial parameters

Default is 9600-8-N-1 (common for Cisco / Huawei / H3C). If the preset library is enabled, pick brand + model and the parameters auto-fill — e.g. Juniper often 9600, some older devices 115200.

1. Click “Open serial” and grant the browser access to the serial device.
2. Adjust baud rate / data bits / parity / flow control, then “Connect” to establish the relay link (auto-connect is available).
3. Fill in the device/site note (required) — engineers see it, e.g. “CR1-RoomA core switch”.

2.4 Session code & approval

• A 5-character Console ID is generated automatically (one letter + four digits, e.g. A1203); “New code” regenerates it.
• Tick “Require my approval” and each join request shows a banner on top with Allow / Deny.
• The field side is always free — unlimited time and concurrency, unaffected by engineer plans.

3Inviting engineers

Send the invite link (or QR code) to the engineer via chat or email — opening it drops them straight into the terminal.

• Invite links look like https://caas.support/console.html?s=A1203; they can also open console.html and type the 5-character code manually.
• Several engineers can join the same session: the first one holds the keyboard, the rest watch in read-only mode.
• You can rotate the code at any time — old links stop working.

3.1 End-to-end encryption (per session)

The field page's encryption panel offers three modes: Off / Link key / Passphrase. Picking one reveals exactly its invite link below (the others stay hidden, keeping the panel compact); a comparison of the three modes is folded under "What's the difference between the three?".

• Link key: a random 256-bit key rides in the invite link's # fragment (never sent to the server) — just share the whole link. Strongest option.
• Passphrase: the link carries no secret — tell them the passphrase over a separate channel; both sides derive the key locally with PBKDF2.
• Off: serial data crosses the relay as plaintext (a yellow banner stays visible). The Android app's invite link is always this mode — use the web field console when encryption matters.
• Changing the key/passphrase mid-session broadcasts a re-key and connected engineers reconnect automatically — no new link needed.

4Engineer terminal

4.1 Join a session

1. Open the invite link, or visit console.html and enter the session code.
2. Choose your identity: anonymous guest, sign in, or continue with your signed-in account.

4.2 Keyboard control

• Only one person types at a time, so multiple engineers never fight over the same prompt.
• The controller can hand over or release control from the top menu; a viewer can “request control” and the controller approves.
• If the controller leaves, control passes to the earliest remaining viewer automatically.

4.3 Everyday actions

• Large pastes: paste multi-line configs straight into the terminal.
• Log capture: “Capture” saves the terminal output to a file for later analysis.
• “Clear” only clears the screen (the device is untouched); “Disconnect” leaves the session.
• Photos, short videos and text sent from the field appear in “Field msgs” so engineers can see the physical setup.

4.4 Access tiers

5Accounts & plans

5.1 Register & sign in

• Register at auth.html with email + password (username optional: 2-24 chars of letters/digits/._-). Passwords are 8-128 characters and stored as salted scrypt hashes — never in plain text.
• Sign in with either email or username; the session lasts 24 hours and auto-renews while you use it.
• Change your password or username from the account panel in the terminal page or auth.html.

5.2 Forgot password

• Use “Forgot password” on the sign-in page: a one-time reset link (valid 30 minutes) lets you set a new password yourself.
• If mail delivery is not configured on the site, ask an administrator to generate a reset link or set a temporary password from the admin portal.
• If an older email account reports “no password set”, set one from the register page with the same email — no duplicate account is created.

5.3 Pro plans & payment

• Pricing: Pro · 30 days — $5, one-time (auto-expires back to free).
• How to buy: pay by card — the “Card” button in the Pro card opens our payment partner’s secure checkout page in a new tab, and Pro is activated automatically right after payment. Alternatively payment can be collected manually and you receive a one-time activation code: click “Redeem” on the landing page (you will be asked to sign in first), or contact the site owner (footer email) to pay.
• Redeem: after signing in, enter the code in the dialog — Pro activates immediately; if your Pro has not expired yet, the new duration is added on top of the existing expiry date.
• A confirmation email is sent automatically after redemption; Pro falls back to free when it expires. Administrators can also grant Pro manually with no expiry.

6Admin portal

Open admin.html and sign in with an admin account (or configure ADMIN_TOKEN as the super key on the server). Admin accounts are protected: revoking or deleting them requires the super key.

6.1 Users tab

• New user: enter email (required), username (optional), password (blank = auto-generate) and plan (Free / Pro). The account is usable immediately; an auto-generated password is shown only once — copy it and hand it over.
• Reset password: set a new one directly, or generate a one-time reset link (valid 30 minutes) to forward to the user.
• Set Pro / Free, make/remove admin, and delete accounts (signs the user out, disconnects live consoles, irreversible).

6.2 Other tabs

• Overview: site status, live connections and per-device participant details (IP, region, duration), refreshed every 6 seconds.
• Activity: join/leave audit for today, last 24 hours or last 7 days.
• Console presets: maintain serial parameters and cabling hints per brand/model; the field page auto-fills from them.
• Activation codes: generate one-time codes in batches after collecting payment (7 days / 30 days / custom days), with per-code copy, copy-all, filter, search and void; redeemed accounts and times are listed here. The “afdian channel orders” section below lists codes created by the payment webhook — orders whose remark carried a registered email were activated automatically, the rest can be copied back to the buyer on afdian (or the email can be resent).
• Feedback: landing-page messages. Billing: online-payment order flow and revenue summary (empty while that channel is closed).

7FAQ

8Support

Entry: https://caas.support · Field: /phone.html · Terminal: /console.html · Admin: /admin.html · Android app: /caas.apk

If something does not work, leave a message with the Feedback form on the landing page (visible under the admin portal's Feedback tab), or contact your site administrator for account issues.