Terms of Service

Who operates TraceWise

RazorSoft, Incorporated operates TraceWise. The service website is https://www.tracewise.dev. Questions go to the support form at https://www.tracewise.dev/support.

The service

TraceWise checks URLs you add, stores the check results, opens and resolves incidents from those results, and can publish a public status page. Scheduled checks run from TraceWise infrastructure on the interval your plan allows. You can also request a manual check when your API key includes that permission.

TraceWise does not promise that every check runs on time, that a status page matches the target at every moment, or that monitoring will be uninterrupted.

Accounts and authentication

Sign-in and sign-up are provided by Clerk. TraceWise stores the Clerk user id, the email address Clerk provides, and an optional name, and it creates a workspace for that user.

The dashboard, monitors, billing, notification settings, and API keys require a signed-in account. The public status page, public embeds, the demo status page, and the WordPress plugin download do not require an account.

Free and paid plans

Workspaces are Free, Starter, Growth, or Scale. The Free plan is shown as $0 per month. Paid prices on the pricing page are the amounts Stripe returns. Paid features apply only while the workspace billing status is Active or Trialing. Otherwise the workspace uses Free limits.

Current limits in the product are:

• Free: 10 monitors, minimum interval 300 seconds, 7-day history window, 1 public status page, email alerts.
• Starter: 50 monitors, minimum interval 60 seconds, 30-day history window, 5 public status pages, and the paid notification channels.
• Growth: 150 monitors, minimum interval 60 seconds, 90-day history window, 15 public status pages, and the paid notification channels.
• Scale: 500 monitors, minimum interval 60 seconds, 365-day history window, 50 public status pages, and the paid notification channels.

Payment

Paid checkout and the billing portal are handled by Stripe. TraceWise stores a Stripe customer id on the workspace when one exists. This page does not add a refund right beyond applicable law. It does not set a trial length, or a cancellation effect on stored monitors and checks, beyond the billing status Stripe and TraceWise already record (including Past due and Canceled).

Monitoring and check results

You choose the monitor name, URL, interval, expected HTTP status codes, timeout, and slow threshold. TraceWise requests that URL and stores the outcome: whether the check succeeded, how long it took, the HTTP status when one was received, and a diagnostic record. That record covers DNS, connection, TLS, HTTP, redirects, and a short explanation. TraceWise does not store the response body of the monitored URL.

You are responsible for having permission to request each URL you add. TraceWise can reject a monitor that exceeds the plan’s monitor cap, interval, or duplicate-URL rule.

Incidents and public status pages

Incidents open and resolve from consecutive check results. An enabled public status page shows the page name, the monitor names and group names you included, uptime figures, and incident start and end times. It does not show workspace settings or the internal diagnostic text.

Anyone with the link can view an enabled public page. The demo slug is a public example. How many public status pages a workspace can create depends on the plan.

API keys, embeds, and WordPress

API keys are created in the dashboard, shown once, and stored as a SHA-256 hash of the key. A key can include scopes such as monitors:read, monitors:write, incidents:read, and checks:run. Keys can have an expiry and can be revoked. Authenticated API use is rate limited, including 10 requests a minute per key and 100 requests an hour and 500 requests a day per workspace, plus tighter limits on some actions.

Public embeds load https://www.tracewise.dev/embed/status.js in the visitor’s browser and then request the published status, history, or incidents for that page’s slug. Those requests do not include an API key.

TraceWise for WordPress can store an API key on the WordPress site, encrypted by the plugin, and send it from the WordPress server to https://www.tracewise.dev/api/v1. Public widgets on a WordPress page do not use that key. The plugin does not send WordPress user accounts, comments, or post content. Uninstalling the plugin deletes its settings and the stored key from that WordPress site. It does not delete the TraceWise account, monitors, or status pages.

Alerts

Free workspaces can send incident email. Paid workspaces can also use the notification channels the plan allows, including Slack incoming webhooks, HTTP webhooks, and device push, to destinations you configure. Alert email is sent with Resend.

Availability and other limits

TraceWise is a monitoring tool. It does not guarantee that a monitored site is up, and it does not guarantee that TraceWise itself will be available. Public status responses can be cached for a short time. This page states no service-level agreement and no security certification.

Changes

RazorSoft, Incorporated can change the service and these terms. The date at the top of this page is the date of this text. The current text is always the page at https://www.tracewise.dev/terms.

Contact

Use https://www.tracewise.dev/support. If you are signed in, the support form receives your TraceWise user id, workspace id, and plan so the request can be matched to the account.