Signed delivery
Outbound events are signed so you can verify the sender, and retried inside a published envelope.
INTEGRATIONS
Send the events, not the telemetry.
Deliver signed alert, audit, and posture events to destinations you own. Raw telemetry rows and destination addresses are excluded.
Context
The situation
Security teams already have a place where events go. A tool that insists on being another console is a tool that gets checked on Tuesdays.
Precyz delivers alert, audit, and posture events to a destination you own: a signed webhook, a chat channel, a security event platform, or a ticketing system. Destination ownership is verified before delivery begins.
On this page
What you get from this
Export is a separate path
A warehouse copy is a tenant-initiated export with documented formats, not an always-on stream to a third party.
Team and Enterprise
Webhook and chat start on Team. Security-event and ticketing destinations are Enterprise.
Collection boundary
The boundary
We observe here
Alert events, audit events, and posture events, tenant-scoped, with the fields listed in the integration profile.
We never collect here
Raw telemetry rows, destination IP addresses, or any field outside the published profile. There is no integration mode that exports raw telemetry.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Not included
Pro
Not included
Team
Webhook and chat
Enterprise
Webhook, chat, SIEM, and ITSM