PULSE
Planned: endpoint signals that device owners can see
Noxtica Pulse is an endpoint client being built for security and observability signals. It is planned to tell device owners what it sends and let them control it.
WHAT IS PLANNED
Planned capabilities
These items describe the design direction. None of them is a commitment on scope or date.
In development
What the tenant sees
- Chooses which signals to enable
- Publishes a notice
- Receives the enabled signals in its console
- Decides what to do about a flag
Between the two
The notice
Explains what is collected and why.
What the device owner sees
- A visible indicator on the device
- A notice before collection
- A view of what it sends
- A choice to accept or decline optional purposes
A hidden mode is not planned.
Signals about the tenant's own application
The client is planned to report integrity and performance signals about a tenant's own application. It would also report network quality on the device.
Visible to the device owner
Pulse is planned to run with a visible indicator, a notice before collection and a view of what it sends. A hidden mode is not planned.
Controls and rights
Device owners are planned to be able to switch purposes off, withdraw consent, export their data and request erasure. Flagged detections would come with a reason and a way to appeal.
PLANNED APPROACH
Planned approach
These steps describe the intended design, not a released workflow.
The tenant
Choose signals, publish a notice
A tenant would choose which signals to enable for its own application, and publish a notice on what is collected and why.
In development
Device owner
Read the notice, then decide
The tenant's notice
A person would sign in with a Noxtica account, read the notice, and accept or decline optional purposes.
In development
Console
Signals reach the tenant
Enabled signals
The client would send the enabled signals to the tenant's console. What to do about a flag would stay with the tenant.
In development
The tenant chooses signals
A tenant would choose which signals to enable for its own application. It would publish a notice explaining what is collected and why.
The device owner decides
A person would sign in with a Noxtica account, read the notice, and accept or decline optional purposes.
Signals reach the tenant
The client would send the enabled signals to the tenant's console. What to do about a flag would stay with the tenant.
WHERE IT WOULD FIT
Questions it is planned to help answer
Fit depends on what the finished scope turns out to be.
Is the application behaving as expected?
Teams could see whether their application runs as expected on a device, within the signals the tenant enables.
Is the problem on the device side?
Teams could separate a poor device connection from a problem in their own service.
Which flags deserve human review?
Teams could review flagged signals and the evidence behind them before any decision about an account.
HOW TEAMS WOULD CONNECT IT
Planned connection model
Nothing here is a supported setup today.
- Tenants would configure signals, notices and review workflows in the Noxtica console.
- Device owners would sign in with their own Noxtica account on the device.
- Early access, if offered, would be arranged directly with Noxtica.
LIMITS
Status and boundaries
Read this page as a description of intent.
- Pulse is in development and is not generally available. Nothing on this page is a commitment on scope or date.
- Signals would be indicators, not proof. They are probabilistic and can be wrong. A client running as an ordinary program cannot observe every kind of tampering. The tenant decides what to do, and no protection outcome is promised.
- The client is planned to notify the device owner and report signals. It is not planned to end sessions or stop programs on the device.
- Customers would be responsible for notices and a lawful basis for their own use. Use on work devices would be off by default and need local legal steps before activation. Watching people without a lawful basis is not permitted.
Assistant and connection output is an estimate and can be wrong. Your team reviews it before acting.Read the disclaimer
FAQ
Questions about Pulse
Can I use Pulse today?
No. It is in development and not generally available. You can ask about early access.
Would Pulse run without the device owner knowing?
No. The design goals include a visible indicator, a notice before collection and a view of what is sent. A hidden mode is not planned.
Is Pulse meant for watching people at work?
No. The planned purpose is integrity and performance signals about a tenant's own application. Use on work devices would be off by default and need local legal steps before activation.
Related products
PULSE
Ask about early access
Early access, if offered, would be agreed directly with Noxtica and subject to legal review. Contact the team to ask.