Where the manual for each product actually is.
Documentation sits with the product it documents rather than on a separate site that falls behind it. This page is the index: four products are running today and have pages you can read, and the other five will get theirs on the day they ship.
Comsky Cloud
Inside the console at cloud.comsky.ai, beside the screen each page describes.
- ·Getting started — create a project, launch an instance, attach a volume.
- ·GPU instances — documented when they come online through 2026
- ·Common tasks — snapshots, resizing, firewall rules, SSH keys.
- ·The REST API and the OpenAPI document that describes it.
Comsky CRM
In the app at crm.comsky.ai, reachable once you are signed in.
- ·Getting started — import contacts, shape your pipeline, connect your inbox.
- ·Common tasks — deal stages, activity types, custom fields, permissions.
- ·Automation — how a workflow fires and how to see why one did not.
- ·The mobile apps, once they leave internal testing
Comsky TallyBridge
With the bridge, at tally.comsky.ai — most of it covers the Windows side.
- ·Getting started — install the bridge, point it at TallyPrime, run the first sync.
- ·What the bridge reads, what it never writes back, and what it sends upward.
- ·Common tasks — adding a second company, inviting staff, scoping what they see.
- ·Troubleshooting — the sync stopped, the numbers disagree, the port is blocked.
Comsky Backup
In the console at backup.comsky.ai, with the agent notes next to the downloads.
- ·Getting started — install the agent, choose drives, set the first schedule.
- ·Restores — single file, whole folder, and a full drive, step by step.
- ·Retention and versions — what is kept, for how long, and what that costs you.
- ·Keys — where the per-device key lives and what happens if you lose it.
Some of it needs an account, because a page about a screen is worth less than the page next to the screen. Creating one costs nothing. If you cannot find something, write to support@comsky.ai and we will answer first and write it up second.
A spec that cannot drift, because nobody types it.
Comsky Cloud is the product with a documented REST API today. Every other product documents its own as it ships.
Every console action has an endpoint
There is no button in the console that reaches something you cannot. The console is a client of the same API you are handed, which is what stops a private back door from quietly appearing.
- ·Instances, volumes, snapshots, networks, keys
- ·GPU instance types requested the same way as any other
The OpenAPI document is generated
It is built from the same route table the server uses to dispatch requests. A route that exists appears in the spec, and a route that is removed leaves it, without anyone remembering to edit a file.
- ·Generated at build, not maintained by hand
- ·Served alongside the API rather than published as a stale file
Tokens carry a scope
A token is scoped to a product and a permission set, is listed with its last use, and is revoked on its own rather than by rotating a secret that everything shares.
- ·Per-customer tokens for partners and MSPs
- ·Revocation takes effect immediately
Generate the client you want
Point any OpenAPI generator at the document and you have a client in your language. We do not publish SDKs yet, and an accurate generated client beats a hand-written one that lags the server.
- ·Plain REST over HTTPS — curl works
- ·JSON in, JSON out, conventional status codes
Documentation arrives with the product.
These five are not running for customers, so there is nothing to document yet and nothing here pretends otherwise. A page describing a screen you cannot open is worse than no page at all.
| Product | What its documentation will cover | Published |
|---|---|---|
| Comsky Telephony | Number provisioning, IVR trees, routing rules, DLT registration and the CRM write-back. | On release |
| Comsky Chat | Connecting the website widget, the WhatsApp number and the shared mailbox; routing and AI drafts. | On release |
| Comsky Books | Company setup, voucher entry, GST returns, e-invoicing and the keyboard shortcuts. | On release |
| Comsky HRMS | Employee records, attendance devices, leave policy, payroll runs and statutory filings. | On release |
| Comsky Monitor | Adding checks, installing agents, SNMP discovery, alert policies and escalation. | On release |
Each product page on this site describes what the product is being built to do. That is a plan, not a manual, and we would rather you read it as one. See every product.
The rules we hold the pages to.
Written against the running build
A page describes what the product does now, not what it did at the last release and not what it will do next quarter. When a screen changes, the page changes with it or the change is not finished.
Task first, feature second
Pages are organised around what you are trying to do — restore a file, add a company, scope a token — rather than around the menu structure, which is our problem and not yours.
No screenshots of things that do not exist
Every image comes from the real console with real data removed. We do not mock up a screen for the documentation and we do not document a setting that is still behind a flag.
Written for Indian operations
GST, DLT, PF and ESI turn up in the examples because they turn up in the work. Amounts are in rupees and dates read the way they are written here.
A person behind the page
If the documentation does not answer it, support does, in IST. A question that reaches support twice is a documentation bug and gets fixed as one.
Changes are announced, not discovered
Anything that changes behaviour you depend on — an API field, a default, a retention rule — is called out rather than silently edited into a page.
What people ask about the docs.
Is there a PDF manual I can download?
No, and there will not be one. A PDF is out of date the day it is exported, and the version circulating in your team is never the one we fixed. Print the pages you need instead.
Can I read the documentation before I sign up?
The product pages on this site cover what each product does and how it works. The operational pages — the ones with the buttons in them — sit with the running app, so some of them need an account. Creating an account costs nothing and does not require a card.
Do you publish SDKs for the API?
Not yet. The Comsky Cloud API is plain REST over HTTPS, and the generated OpenAPI document produces a client in most languages. When we publish an SDK it will be generated from that same document rather than written separately.
A page is wrong or missing. What do you do about it?
Tell us at support@comsky.ai. We treat a wrong page as a defect against the product rather than a typo, because if the page is wrong the behaviour it describes probably surprised you too.
Will there be documentation for the coming products before they ship?
No. We publish it when the product is available to customers. Writing the manual for software nobody can open is how documentation and reality part company in the first place. The pages are in English; support answers in Hindi and English if reading it is the obstacle.
Read it with the product open.
The four live products document themselves from inside the console. Create an account and the pages are one click from the screen they describe.
Support answers in IST, at support@comsky.ai.