These terms govern your use of CloudMonitor, a service that connects to cloud accounts you control and reports on their configuration, certificate and secret rotation posture. Three sections matter more than the rest and are written to be read rather than skimmed: section 3, on what state the service is actually in; section 5, on the access you grant us; and section 6, on what you must be authorized to do before you connect anything.
CloudMonitor is operated by Peripatetical, a sole proprietorship based in Hawaii ("we", "us"). By creating an account, connecting a cloud account, or using the service, you agree to these terms. If you are agreeing on behalf of an organization, you confirm you have authority to bind that organization, and "you" means that organization.
Who that actually is. CloudMonitor is run by Peripatetical, a sole proprietorship based in Hawaii, United States. Peripatetical is the party you are contracting with. We have filed to form Peripatetical LLC: our articles of organization were filed with the Hawaii Department of Commerce and Consumer Affairs on October 3, 2026, and Hawaii's business registry is experiencing processing delays, so approval is still pending. When the State of Hawaii approves the filing, Peripatetical LLC takes over the business and we will update this page. When Peripatetical LLC's formation is approved, Peripatetical will transfer these terms, your account and any subscription to Peripatetical LLC. Nothing changes for you: the same terms, prices and data handling continue, and you do not need to do anything. The business is an independent two-person business: the owner, with help from a family member. The person who would normally answer a support ticket is the person who wrote the software.
We say this plainly because it is the single most useful thing a security review can know about a vendor it is about to hand cloud credentials to. Weigh it.
CloudMonitor reads configuration and metadata from cloud accounts and endpoints you connect, and presents findings about posture, expiry and rotation — for example certificates approaching expiry, secrets past their rotation policy, and resources configured in ways we flag as risky.
CloudMonitor is a monitoring and reporting tool, not a guarantee. It reports what it observes through the access you grant, when it runs. It does not detect every problem, does not act on your infrastructure, and is not a substitute for your own security program, monitoring, or incident response. You remain responsible for your infrastructure.
Two details about when it runs, because they are easy to assume wrongly:
Scan frequency is not a service level. We may change how often any check runs, and a check may be delayed, skipped or fail without notice. Nothing in this section is a commitment to detect a problem within any particular time, or at all.
CloudMonitor emails the people on your account when it finds a critical condition — an endpoint it could not reach, or a certificate approaching expiry. On your Alerts & notifications page you choose how far ahead expiry warnings begin, how often a repeat notice about the same item may be sent, and whether to receive them at all, per type of alert. Anything that expires follows a fixed escalation ladder — 90, 60, 30, 14, 7 and 1 days ahead, then on the day itself — applied the same way to certificates, vault secrets and keys, storage keys, other tracked credentials and domains. Your window narrows that ladder from the top; it decides how far ahead the first notice arrives, not whether the later ones do. Notices about the same item are deduplicated; an item moving to the next step of the ladder is treated as new information and is sent again. When a condition clears we send a recovery notice, unless you have switched that type off.
You can additionally send findings to a Slack incoming webhook, Microsoft Teams, Discord, PagerDuty or a webhook URL of your own, or have them opened as tickets in your ConnectWise, Autotask, HaloPSA or NinjaOne account. Those are your integrations with your providers; what you send and where is your choice, and our Privacy Policy describes what leaves our systems when you use them.
CloudMonitor is a new service, run by a small team, and these terms describe it as such. Read this section before you rely on anything else in this document.
Sign-in is handled by our central identity service at auth.peripatetical.com. There is no CloudMonitor password: signing in means signing in there, and managing or resetting your sign-in method happens there rather than here. You are responsible for keeping control of the email address you sign in with, and for the actions of every user you invite into your account.
Your account at the identity service is shared across our products. Deleting your CloudMonitor data does not delete that account; the Privacy Policy explains how to ask for both.
Accounts are organized into tenants. A tenant administrator can invite users, connect and disconnect cloud accounts, and see all findings for that tenant. Choose your administrators accordingly.
The public demo account is not your account. The read-only demo reachable from the sign-in page runs on shared, fabricated data. It is not private, it is not yours, and nothing you do in it is confidential. Do not put real information into it.
To do anything useful, CloudMonitor needs read access to the cloud accounts you want monitored. Depending on the provider, that means a service principal secret, an access key, a service-account key, or a role you grant to our identity.
Reader and Monitoring Reader roles on
Azure, read-only Microsoft Graph application permissions (granted by your
directory admin) for Microsoft 365 and Entra ID, the SecurityAudit
policy on AWS, a dedicated read-only service account on Google Cloud and
Kubernetes, a read-only registry token or a mutual-TLS connection to the Docker
Engine API for Docker, and a Connected App with read-only scopes for MuleSoft
Anypoint. CloudMonitor does not create,
modify, or delete resources in your cloud.Deleting a connection here. An account admin can disconnect any connection from the Connections page, and disconnecting deletes the stored credential along with it. If you cannot do that yourself, revoke the credential at your provider first, then open a support ticket (in the product under Support, or through our support page if you are not signed in) and we will delete the record.
For HTTP endpoint monitors that need authentication, the stored credential is shown to your users in masked form only; no user in your account can reveal it. The operator's own owner account can reveal one — for example to diagnose an authenticated check that keeps failing. Reveals are rate-limited and every one is recorded with the user, time, IP address and browser. Each reveal also appears in your account's Activity log as a CloudMonitor support entry, with the endpoint and the time. The IP address and browser stay in our record; ask and we will give you those for your endpoints.
An honest limit. Encryption at rest protects your credentials against compromise of our database or its backups. It does not protect against compromise of the running application, which by necessity can decrypt them. We will not claim otherwise. Grant the narrowest access that makes the product useful to you, prefer federated identity over long-lived keys where your provider offers it, and rotate on your own schedule.
Our Privacy Policy describes what we collect, who processes it, and how long we keep it.
You may only connect cloud accounts and endpoints that you own or are expressly authorized to monitor. Scanning infrastructure without authorization may be unlawful in your jurisdiction and in the jurisdiction where the infrastructure sits.
You are solely responsible for holding that authorization. If we believe a connection is unauthorized, we may suspend it immediately and without notice. Section 14 covers your responsibility for claims that arise from an unauthorized connection.
You agree not to:
Usage limits exist so that one account cannot exhaust a shared resource. If you have a genuine reason to test the service harder than that, open a support ticket (in the product under Support, or through our support page if you are not signed in) first.
API keys. Every plan includes API access: an account administrator can create keys that let your own software read your account's data. A key can only read: it cannot change anything in the service or in your cloud. Keys are credentials. Keep them secret, give them only to software you control, and switch off any key you think has been exposed. Every key expires. We may switch off a key we believe is exposed or being misused, and we will make reasonable efforts to tell you when we do. Each key is rate-limited, and the limits are shown in your account. The API is covered by sections 9, 13 and 14 like the rest of the service: it carries no separate availability commitment. We intend to keep version 1 of the API stable; we may add to it, and we will announce a change that would break an existing integration in advance, under section 16.
Network Tools. You may use the latency, HTTP and port-check tools only against systems you own or administer, or that you have the owner's written permission to test. You must not use them to scan third parties, to look for vulnerabilities you are not authorized to test, or to get around their limits. We record who ran each check and against what, and may suspend the tools or your account if they are misused or if we receive a credible abuse report.
What the pricing is. Current pricing is published at /pricing. You are billed on units, not on a raw count of resources. Each resource the service monitors is weighted: a core resource (such as a virtual machine, database, Kubernetes cluster, application host or load balancer) is 1 unit, and a supporting resource (such as a secret, key or certificate, monitored endpoint, storage bucket, disk, DNS zone, security group or public IP address) is 0.2 of a unit. The weights are added up and the total is rounded up to a whole number. Which kinds of resource are counted, and which are core or supporting, is set out on the pricing page.
Bands. The monthly fee is a flat amount set by the band your unit count falls in: Starter, US$29 per month, up to 25 units; Team, US$99 per month, up to 100 units; Business, US$299 per month, up to 500 units; Scale, US$749 per month, up to 2,000 units. The smallest band is the minimum fee; there is no separate minimum and no charge per resource or per unit. Above 2,000 units, pricing is by arrangement rather than self-serve.
How your band is determined. The unit count is measured by the service, which records it once a day. The band charged for a billing period is the one that the last unit count recorded in that period falls in — not the highest count during the period and not an average. A count that rises above, or falls below, a band boundary therefore changes the fee for that period only if it is still the case at the last count before the period closes.
Spend ceiling. You may choose a ceiling: the highest band you agree to be charged for. From the first daily unit count recorded after you set it, the fee for a billing period will not exceed that band’s fee, whatever your unit count. If your unit count stays above the ceiling for 14 days (or, if it goes above the ceiling again within 30 days of a pause, straight away), we will email your billing contacts a warning, and no sooner than three days after that warning has been delivered we will pause monitoring of the account, subscription, project or cluster you connected most recently (and, if that is not enough, the next most recent) until your unit count fits under the ceiling. We will also email them when you first exceed the ceiling and when a pause takes effect. A paused connection is not monitored, alerted on or counted. You can raise or remove the ceiling, or resume a paused connection when there is room for it, at any time from the billing page.
Add-ons and changes. Optional add-on features are priced separately and listed on the pricing page. Where a plan includes a feature up to a monthly fair-use allowance (such as Deep Analyze), use beyond the allowance is paused until the next calendar month and is never charged. Published pricing may change; a change to your rate will be notified in advance under section 16.
Advanced assistant overage. If your account has the advanced assistant overage add-on, the advanced assistant keeps answering after your plan's monthly allowance is used. Overage is measured in blocks of advanced assistant use priced at US$0.15 each, billed in arrears, and stops at the monthly limit you set on the billing page, after which the assistant uses the standard model until the next calendar month. Without the add-on, the assistant uses the standard model once the allowance is used. Nothing is charged for staff support sessions.
Free trial. A new account starts a 14-day trial. No card is required to start it, and it does not convert into a paid subscription by itself.
Payments will be processed by Stripe as merchant of record. We intend to sell through Stripe Managed Payments, under which Stripe's merchant-of-record service — not us — is the seller of record for your purchase. That is not a formality, and it changes some things you would otherwise expect:
Cancellation and refunds. You can cancel a subscription at any time; cancellation takes effect at the end of the paid period and there is no termination fee. If the service materially fails to do what we said it would within the first 30 days of a subscription, open a support ticket (in the product under Support, or through our support page if you are not signed in) and we will arrange a refund of the relevant fee. Beyond that, and except for annual plans (below), fees already paid are non-refundable except where required by law or where Stripe's own policies provide otherwise. Any bespoke commercial arrangement — a pilot, a discount, a committed term — only binds us if we have put it in writing.
Annual plans. If you pay for a year in advance and cancel before the year is up, your plan ends at the end of the month you are in, and we refund what you paid less the regular monthly price for each month you have started, minus the payment-processing fee on the refunded amount (currently 6.4%). If nothing is left after that, there is no refund. Refunds go back to the original payment method.
When a prepaid plan changes band. If you pay for a band a month or a year in advance, your plan follows your unit count, up and down. Up: if your unit count goes above your band, we email your billing contacts with a date at least 7 days later. If it is still above the band every day until that date, your plan moves to the band your unit count is in on or after that date, and when it moves we charge the difference between the two bands’ prices for the rest of the current month or year. If that date falls after your current month or year ends, your plan first renews at your current band as usual, then moves up on or after that date, and we charge the difference for the rest of the new month or year. If that date falls in the last two days before your plan renews, it instead renews at the higher band, at its full price, and nothing extra is charged before then. If your count falls back within your band before then, nothing changes and nothing is charged. Your plan never moves above a spend ceiling you have set (see above). Above 2,000 units it does not move by itself and we contact you about pricing, unless you have set a spend ceiling, in which case it moves up to your ceiling’s band at most. Down: if your unit count at the end of a month or year fits a smaller band, your plan renews at the smaller band’s price. Nothing already paid is refunded for a move down.
We do not offer a service level agreement. We do not commit to a specific uptime percentage, scan frequency, or detection latency, and we may perform maintenance that interrupts the service.
If our hosting provider fails, we may move the service to a standby with a second provider. While it runs there, changes made in roughly the hour before the failure may be missing, and scheduled scans, checks and alerts pause until the service is back on its usual provider. Moving back may briefly take the service offline. What you would see is described on our security page; the times given there are targets, not a commitment.
We say this plainly because it matters more for a monitoring product than for most software: you must not rely on CloudMonitor as your only means of learning that something is wrong with your infrastructure. If you need a contractual availability commitment, talk to us before you buy rather than after. No statement on our website, in the product or in an email is such a commitment unless it is in a written agreement signed by us.
The service may be discontinued. If that happens we will give account holders reasonable notice where we can, and a chance to get their data out.
As between you and us, you own your data — your account information, your credentials, and the findings generated from your infrastructure. You give us only the permission needed to run the service for you: to store what you connect and configure, to scan it and return findings, and to pass what is necessary to the service providers named in the Privacy Policy. That permission is limited to operating the service, ends when you delete the content or your account (subject to the retention periods in the Privacy Policy), and covers nothing else.
We treat your configuration data and findings as confidential. We do not sell it, we do not use it to train machine-learning models, and we do not share it with third parties except the service providers listed in the Privacy Policy, the alerting destinations you configure yourself, or where we are legally required to.
Getting your data out is a button. An account admin can download everything the account holds — users, alert settings, endpoints, connection details, API key details, findings and scan history, cost history, support tickets and billing records — as one machine-readable ZIP file from Settings › Your data, whenever they like. With the API, included in every plan (section 7), your own software can also read findings and configuration directly. Stored credentials, keys and tokens are deliberately excluded from every export and from the API, and the file’s manifest says what was left out. If you are not an account admin, or cannot use the page, open a support ticket (in the product under Support, or through our support page if you are not signed in) and we will run the export for you.
We own CloudMonitor — its software, interface, documentation and the CloudMonitor and Peripatetical names. These terms grant you a limited, non-exclusive, non-transferable right to use the service while your account is in good standing, and nothing more. You own your data; we own the tool. Third-party names and marks are used only to identify their owners' products.
If you send us feedback or a feature suggestion, we may act on it without owing you anything for it. You do not lose any rights you already hold by telling us something is broken.
These terms apply for as long as you have an account. You may stop using the service at any time, and an account admin can close the account without asking us: Settings › Your data › Delete my account stops the service at once and permanently deletes the account’s data after 30 days, during which an account admin can restore it; “Erase now” deletes it at once, with no undo. It will not run while a subscription is still running, or for an account that includes platform staff; for those, open a support ticket (in the product under Support, or through our support page if you are not signed in) and we will do it. Download your data first if you want a copy.
We may suspend or terminate an account that breaches these terms, that we reasonably believe is being used unlawfully, or for non-payment. Where practical we will give notice and a chance to respond first; for suspected unauthorized scanning (section 6) or a risk to the security of the service we may act immediately.
When an account is cancelled or its subscription ends (including when a payment cannot be collected), we keep its stored cloud credentials for 30 days, so that it can be reactivated without reconnecting anything, and then delete them; after that, reactivating means reconnecting your cloud accounts. When an account admin deletes the account, they are deleted at once. Findings and account records are handled as set out in the Privacy Policy. Before you go, an account admin can download the account’s data from Your data as a machine-readable file; if that is not possible, ask us and we will send it. The sections that by their nature should survive — your data and confidentiality, intellectual property, warranties, limitation of liability and indemnity, governing law and disputes, and the general terms — continue to apply after termination.
To the fullest extent permitted by law, the service is provided "as is" and "as available", without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose, accuracy and non-infringement.
We do not warrant that the service will be uninterrupted or error-free, that it will identify every misconfiguration, expiring certificate or unrotated secret in your environment, that an alert will be sent or delivered, or delivered in time, or that its findings will be free of false positives or false negatives. Remediation guidance and suggested commands shown in the product are information, not advice: you decide whether to run them, you run them yourself, and you are responsible for the result.
Nothing in these terms excludes liability that cannot lawfully be excluded — including for fraud, or for death or personal injury caused by negligence. Some jurisdictions do not allow certain exclusions, so parts of this section and the next may not apply to you, and your statutory consumer rights are unaffected.
To the fullest extent permitted by law, neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill, arising out of or relating to these terms or the service, even if advised of the possibility.
Our total aggregate liability arising out of or relating to these terms or the service is limited to the greater of (a) the fees you paid us in the twelve months before the event giving rise to the claim, or (b) one hundred United States dollars (US$100).
In particular, and without limiting the above, we are not liable for a security incident, outage, expired certificate or compromised credential in your infrastructure that CloudMonitor did not detect or did not report in time. That is the nature of a monitoring tool offered without a service level agreement, and it is reflected in the price.
You will indemnify us against third-party claims, and the reasonable costs of dealing with them, arising from your connecting a cloud account or endpoint you were not entitled to monitor, or from your breach of section 7.
These limits apply only as far as the law allows; section 13 lists what is never excluded.
Talk to us first. Before starting any proceeding, send us a written description of the problem — through a support ticket, or in writing to [email protected] — and give us 30 days to put it right. If we have a dispute with you, we will do the same by email to the address on your account. Most problems are cheaper to fix than to fight.
You are a consumer if you use CloudMonitor mainly for personal, family or household purposes and not for a trade, business, craft or profession. Otherwise you are a business.
Which law applies. These terms, and any dispute or claim (including a non-contractual one) arising out of or in connection with them or CloudMonitor, are governed by the laws of the State of Hawaii, United States, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
The governing law is that of Hawaii, where Peripatetical is based, so it is the law that already governs the business you are contracting with. One predictable set of rules is fairer to everyone than rules that change with where each customer happens to be.
If you are a consumer. Nothing in this section takes away the protection of the mandatory law of the country — and, in the United States, the state — where you live, or your right to bring or defend a claim in the courts of that place. You are not required to arbitrate. If, after a dispute has arisen, you would prefer arbitration, we will agree to it on the arbitration terms in the next paragraph, and we will pay the arbitration fees to the extent the applicable consumer rules require.
If you are a business. Any dispute between us that is not resolved informally within 30 days after one of us gives written notice of it under "Talk to us first" will be finally resolved by binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, before one arbitrator, seated in Honolulu, Hawaii, in English. The arbitration will be conducted on documents and by videoconference unless the arbitrator finds an in-person hearing essential; neither party can be required to travel. Judgment on the award may be entered in any court with jurisdiction. Claims may be brought only on an individual basis; the arbitrator may not consolidate the claims of different customers or preside over any class or representative proceeding.
Always allowed. Either of us may (a) bring an individual claim in a small-claims court that has jurisdiction over it; (b) ask any court with jurisdiction for an injunction or similar urgent relief to protect intellectual property or confidential information, or to stop unauthorized access to systems; and (c) report a matter to a regulator or law-enforcement body.
If any part of this section is found unenforceable as to a particular claim or person, the rest of it still applies, and that claim proceeds in a court with jurisdiction, under the law chosen above so far as that choice is enforceable.
We may update these terms. If a change materially reduces your rights or increases your obligations — including changing the contracting party under section 1 or changing section 15 — we will give account holders reasonable advance notice, by email to the address on the account or by an in-product notice, before it takes effect. Continuing to use the service after a change takes effect means you accept the updated terms. If you do not accept them, stop using the service and open a support ticket (in the product under Support, or through our support page if you are not signed in) about a pro-rata refund of any prepaid fees. The date at the top of this page always shows the current version.
Questions about these terms: open a support ticket (in the product under Support, or through our support page if you are not signed in). Formal legal notices may be sent in writing to [email protected].