Terms of Service

These terms are the agreement between you and ProcBoss, the operator of ProcBoss Cloud, for use of the hosted service at procboss.com and cloud9000.procboss.com, the ProcBoss dashboard, the @procbossbot Telegram bot, and any bot we operate on Discord (together, the “service”). By creating an account, linking a server, or otherwise using the service, you accept these terms on behalf of yourself or the organization you are authorized to represent.

The pboss CLI and agent are open-source software under their own license; these terms govern the hosted cloud layer, not the open-source project. If a feature or integration (a bot, a deploy provider, a notification channel) has its own terms or configuration, those apply to that piece in addition to — not instead of — this agreement.

ProcBoss Cloud is a monitoring and control plane for your own servers. The agent you install on each machine connects outward to the service and reports server health, process states, crash and threshold events, deployment results, and the log lines you request. Through the dashboard and the bots you can view that telemetry, tail logs, trigger deploys, and start, stop, restart or kill processes.

The service is a window into your fleet and a remote control for it. It is not a hosting provider, not a backup service, and not a guarantee that your software stays up. Monitoring tells you what happened; it does not prevent it.

You must be at least 18 years old, or the age of majority where you live, to create an account. Accounts are created through GitHub or Google single sign-on — we store no passwords. You are responsible for keeping access to that SSO account secure, for the accuracy of the name and email it exposes, and for all activity performed under your account, including by teammates you grant panel access to.

One account per human. Registering service, bot, or duplicate accounts to skirt plan limits or trial conditions is not permitted and may result in termination of every account involved.

The agent runs with the operating-system permissions of the user you installed it as. Restart, stop, kill and deploy actions you trigger through the dashboard or the bots are executed on your machines, under those permissions, on your instruction. You accept the consequences of process control: a killed process stays down until something restarts it; a stopped deployment stops serving traffic.

Connect only machines you own or are authorized to manage. The service is a control plane for your own fleet — not a means to reach, probe, or load someone else's infrastructure. You remain solely responsible for the software you run, the data those machines hold, and complying with the laws that apply to them.

Use the service to operate your own software. You will not use it to break the law, to attack or interfere with any system or network, to distribute malware or other harmful code, to mine cryptocurrency on machines you do not own, to harass anyone, or to infringe intellectual property.

You will not unreasonably burden the service: no scraping of the panel, no automated load we did not agree to in writing, no billing abuse, no attempts to bypass plan limits, rate limits, or access controls. We may enforce these rules with rate limits, feature suspension, or account termination, and we may report illegal activity to the authorities where required.

Every account starts on a free trial of the Growth plan — the full feature set, for a fixed number of days, with no payment details collected up front. When the trial ends, the account settles onto the Free plan unless you choose a paid one; nothing is charged automatically.

Each plan carries quotas — servers, processes, alert channels, history depth — as published on the pricing page at the time you subscribe. Quotas and free-tier features may evolve with the product; a paid plan's price never changes mid-term. Exceeding a quota results in the honest version of a wall: the thing that is over the limit stops syncing or sending until the count comes back down or the plan is raised.

Paid plans are billed by invoice, monthly or annually, in advance. Annual billing carries a discount against the monthly price, as published on the pricing page. Prices are exclusive of applicable taxes, which are added where the law requires, and payments are handled through the payment channels we support — your payment details are processed by those providers, not stored by us beyond the billing record.

If a price changes, we tell you before your next renewal; the new price applies from that renewal onward, never retroactively. If an invoice goes unpaid past its due date we may suspend the account after reasonable notice — suspension pauses alerts and control features; your data is not deleted, and closing the invoice restores the account.

If a charge ever lands wrong — a duplicate, a plan you did not mean to buy — our refund policy exists for exactly that: see the refund policy.

Your servers, your code, and the data on them stay yours. ProcBoss never accesses your repositories or source code, and the agent only reports what it is designed to report (see the privacy policy for exactly what that is). To operate the service we need a limited license to transmit, store, and display the telemetry you send us — you grant us that license for the sole purpose of providing ProcBoss Cloud, and it ends when the data is deleted.

The service, its interface, and its documentation are ours — © 2026 ProcBoss. The pboss CLI and agent remain open-source under their project license. You may not remove or obscure attribution, resell the service without written agreement, or build a competing monitoring product on our API without permission.

Sign-in runs through GitHub and Google; alert delivery runs through Telegram and Discord; hosting and data storage run on commercial cloud providers; deploys run against the git hosts you connect. Each of those is governed by that provider's own terms as they apply to your account with them. When you link one of these services through ProcBoss, you authorize the connection, and you can revoke it from the dashboard — or at the provider — at any time.

We run the service with care, and we maintain a public status page — but the service is provided as-is. Free tiers carry no uptime commitment. Paid plans get the reliability described on the pricing page at the time of purchase. Planned maintenance is announced in advance when practical; emergencies are not.

Monitoring is best-effort observation of systems we do not control. Metrics can lag, agents can drop, alerts can arrive late or — in the worst case — fail to arrive. ProcBoss is a safety net, not a substitute for your own operations, backups, and incident response.

The product will evolve: features appear, retire, and move between plans. We may patch, reconfigure, or restore the service at any time, including for security. We may suspend or restrict an account that threatens the service's security, materially breaches these terms, or burdens other customers — with notice where practical, and without it when the risk is live.

You can stop at any time: unlink servers, disconnect chats, cancel subscriptions, or delete your account — no lock-in, no exit fee. We can terminate for abuse or non-payment, with notice where practical.

On termination your integrations disconnect and your fleet data is removed as described in the privacy policy; the parts of this agreement meant to survive (payment obligations, liability limits, your grants of data license already used) do survive.

To the maximum extent permitted by law, the service is provided without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. ProcBoss does not own your uptime: we are not liable for lost revenue, lost data, lost goodwill, or damage arising from actions taken — or alerts that failed to arrive — through the service.

Our total liability for any claim is limited to the amount you paid us in the twelve months before the event. Nothing in this agreement limits liability that cannot be limited by law, and nothing here removes rights that consumer law gives you permanently.

If a third party comes after us because of how you used the service — a claim that your content or your machines infringed their rights or broke the law — you will defend and cover us to the extent the claim arises from your conduct. This does not apply to disputes between us about the service itself, and it does not apply where we caused the problem.

If something goes wrong, write to us first — nearly everything is fixable by a human with access to the logs. The parties will try in good faith to resolve a dispute for thirty days before starting court proceedings. These terms are governed by the laws of the jurisdiction where the ProcBoss operator is established, without regard to conflict-of-law rules, and the courts of that jurisdiction hear disputes that negotiation cannot settle — without prejudice to mandatory consumer protections in your country of residence.

We may update these terms as the service and the law evolve. Material changes are announced in the service or by email before they take effect; continued use after the effective date is acceptance. The “last updated” line above is the audit trail, and the previous version is available on request.