Make an informed monitoring decision.

Firebase Authentication establishes user identity. The API applies organization membership and role checks to organization-scoped operations. Roles distinguish owner, admin, write, and read access.

Project API tokens and cron check-in tokens are stored as SHA-256 hashes. Complete values are returned at creation or rotation. Keep these values private: a cron URL contains a credential, and a project token grants the access associated with it.

The frontend sets content security, transport, frame, and content-type headers. These controls support application security; they do not establish that every deployment or customer configuration is secure.

Account and organization

Firebase Authentication provides user identity. The application stores account profiles, organization membership, roles, and monitoring configuration in its database.

Checks and results

Runners use the target URLs and settings you configure. Results can include timings, status codes, error messages, security findings, and execution evidence. Information returned by your target may therefore appear in monitoring history.

Browser and inference checks

Playwright tests can produce screenshots, logs, traces, or video according to their configuration. Authenticated recordings require an explicit sensitive-artifact setting. Inference checks send the configured prompt to the selected provider and record response evidence.

AI analysis

When AI root-cause analysis is used, monitoring signals such as errors, timings, historical baselines, and trace messages are sent to Gemini through Google Cloud Vertex AI to generate an analysis. Review errors and traces for sensitive content before using this workflow.

Notifications and public status

Configured notification channels receive alert information. A public status page exposes the services and incident information selected for publication. Review both destinations before connecting a sensitive service.

Billing

Paid subscription billing integrates with Stripe. Subscription and customer references are associated with the organization in Telesis.

Use dedicated test accounts and non-sensitive prompts where possible. Do not put live credentials into test output, alert messages, or material you publish on a status page.

Endpoint security checks observe the configured target from the outside: TLS, certificates, headers, DNS posture, protocols, and exposed technology. Findings help a team prioritize investigation and remediation.

Run checks only against targets you are authorized to test. Endpoint evidence does not provide a complete cloud account inventory, a penetration test, or proof of regulatory compliance.

For retention, deletion, data residency, subprocessors, privacy terms, or a data processing agreement, contact the founder before relying on a specific arrangement. Product controls and plan descriptions do not replace agreed legal terms.

For a suspected vulnerability in Telesis, start with a brief description of the affected surface and request a suitable private channel. Remove live credentials and customer data from the initial message.