Techservice.cloud is an async-managed infrastructure platform for business websites, production apps, and agency client servers.
Use this section when you need the shortest path from product direction to implementation decisions.
Reading path
| Step | Read | Outcome |
|---|---|---|
| 1 | Architecture | Understand the system model and core stack. |
| 2 | API boundaries | Know which system owns each class of data and action. |
| 3 | Provisioning | Understand how long-running server work is queued and tracked. |
| 4 | Dashboard | Align new pages to the client portal UI direction. |
| 5 | VPS and server surfaces | Keep the VPS list and server detail pages scoped to supported actions. |
Product jobs
The web app has two jobs:
- Help customers request and manage isolated hosting infrastructure.
- Give operators a clear control plane for provisioning, monitoring, backups, support, and account management.
Dashboard language
Use language that maps to the user-visible operation.
| Prefer | Avoid |
|---|---|
| Create server | Execute provider workflow |
| Sync inventory | Poll external APIs |
| Manage backups | Configure backup subsystem |
| Open support request | Create handoff record |
Before adding a page
Every new dashboard page should answer these questions:
- What object is the user trying to inspect or change?
- Which system owns the data behind this action?
- Can the connected API actually complete the action?
- Should this be a table, a detail page, or a focused form?