Two businesses in one company.
An IT firm runs its own infrastructure and its own sales desk, and then does the same job again for every customer it looks after. Comsky is sold so that the second one is a business rather than a favour: the same products, bought from a pool at a discount, resold at your price.
What you run for yourself
Your own VMs and GPU jobs, your own machines backed up, your own sites and servers watched. One account, one login, one GST invoice at the end of the month instead of four.
What you resell
Every customer is a workspace under your account. You provision, you support, you invoice. We bill you for the pool and stay out of the conversation you are having with them.
Compute, copies, and proof it is all still running.
Three products cover almost everything an IT firm is actually paid to do. Cloud and Backup are live today. Monitor arrives in 2026 and closes the loop — until it does, the first two stand on their own.
Comsky Cloud
NVIDIA GPU instances, virtual machines and bare metal in Indian data centres, provisioned in minutes and billed by the hour. Spin a customer up without a procurement cycle, and hand the machine back when the project ends.
Comsky Backup
An agent backs up whole drives into per-device encrypted storage that the machine itself has no permission to delete from. When a customer’s laptop is encrypted by ransomware, the copies are not.
Comsky Monitor — 2026
Website and API uptime, server and VM agents, SNMP devices and log alerts on one console, with escalation over WhatsApp, SMS or voice to whoever is on call. Not shipped yet; this is what it is being built to do.
Telephony, Chat, Books and HRMS are also on the 2026 list. Nothing on this page assumes they are running.
A dead VM, a missed backup and a down website are the same problem.
They are the same problem because they all end with a customer ringing you. The point of buying the three from one vendor is that they raise alerts into one place, routed to the person on call on your side.
Provision
Create the instance, deploy the backup agent, add the monitor. From the console or the API, with no Comsky engineer in the loop.
- ·REST API for every console action
- ·Scoped tokens per customer
Protect
Schedules, retention and verification are set per customer, not per technician’s memory. A job that did not run is an alert, not a silence.
- ·Per-device encryption keys
- ·Versioned restore points
Watch
Uptime checks, agent metrics and log rules on the same console that holds the machines. Planned for the Monitor release rather than available today.
- ·Per-customer alert policies
- ·Escalation to the person on call
Prove
Per-customer reports showing uptime, restore drills and resource spend. This is the evidence that gets the contract renewed without a negotiation.
- ·Scheduled monthly reports
- ·Status pages carrying your branding
You buy a pool. You set the price. You send the invoice.
There is no commission and no rate card you have to quote from. You commit to a resource pool, the discount grows with it, and the difference between our price and yours is yours to decide.
Commit a pool, earn a discount
The commitment is to capacity, not to named customers. The discount grows with the pool, to 25 % at the top band, which is the room you need to undercut our list price and still earn on every machine.
Your prices, your invoices
You decide what a customer pays and you bill them yourself. We bill you for the pool. Your customers never see our pricing unless you choose to show them.
Multi-tenant workspaces
Switch between customers without signing out, and never see two customers’ data in one view. Device lists, job history and billing lines stay separated per workspace.
Isolation you can point at
The same fail-closed tenant isolation that keeps our customers apart keeps yours apart, enforced in the database rather than in the interface.
We do not sell around you
A customer provisioned under your account is yours. Escalations come to you first, and we do not approach them separately. That is the whole arrangement.
One agreement, multiple products
Sign once and you can add any of them to your catalogue as it becomes available. No fresh contract for each product you decide to carry.
What this replaces.
Most IT firms arrive here from one of two places: a shelf of unrelated vendor contracts, or a stack assembled abroad and repriced for an Indian customer.
| Separate vendors | A stack bought abroad | Comsky | |
|---|---|---|---|
| Contracts to manage | One per product, renewing on their own dates. | One, priced and supported in another timezone. | One agreement covering every product. |
| Where the data sits | Wherever each vendor happens to host. | Usually outside India. | Indian data centres. |
| Operating many customers | A console per product, a login per customer. | Often built for the end customer, not the operator. | One reseller console with every customer under it. |
| How you make margin | Commission, where it is offered at all. | A referral fee. | Buy from a committed pool at up to 25 % off and sell at your own price. |
| Who invoices the customer | Typically the vendor. | The vendor. | You do. |
| Who the vendor talks to | Varies by vendor. | Your customer, directly. | You. We do not approach a customer provisioned under your account. |
The other half of an IT firm is selling.
An MSP contract is a long, quiet pipeline: a site survey, a quote, three months of follow-up, then a renewal every year after that. The same suite covers that side too.
Comsky CRM
Deals, contacts, companies, inbox, tasks, sequences and reports on one record. Keep a renewal date on the account rather than in a technician’s calendar, and see which quotes are sitting untouched. Live today as a web app that works in a phone browser.
Comsky Telephony — 2026
Virtual numbers, IVR, routing, recording and call analytics on Indian carriers, writing back to the CRM record the call belongs to. Being built so a support line and a sales line share one history instead of two. Not available yet.
Where an IT firm usually starts
What IT firms ask before signing.
Can my own infrastructure sit on the same account as my customers?
Yes. Your own workspace is one more workspace under your account tree, drawing from the same pool. Most partners run it that way, because it means one invoice and one place to look.
Three of the products I want are not shipped yet. What do I do now?
Start with what is running — Cloud, Backup, CRM and TallyBridge — and add the rest as they land. Your agreement already covers them, so adding a product later is a catalogue decision rather than a contract negotiation.
Do I have to resell every product?
No. Carry the ones you can support. An MSP that only ever sells Backup and Cloud is a normal partner, not a lesser one.
Who does my customer call when a restore fails at midnight?
You do, first line, because it is your contract and your relationship. We support you behind that, in IST, and we do not need to speak to your customer unless you want us to.
How large a commitment does this start at?
A pool sized to your existing book. There is no per-customer minimum and no sales target to hit; the bands simply reward a larger commitment with a larger discount, up to 25 %.
Can I put my own branding on it?
Status pages and customer reports can carry your branding today. Full white-labelling of the consoles is on the roadmap rather than shipped, so ask us where it stands before you promise it to a customer.
Run it for yourself first.
Put your own machines on Cloud and Backup, see how they behave for a month, and then decide whether you want to sell them. That is the order most partners do it in.