Truth before theater
Product, provider, release, legal, security, and certification statements remain bounded by the evidence that supports them.
About Dayrook
Built around the people responsible for every client.
Dayrook’s focus is the daily work of MSP owners, service managers and technicians: understanding the client, deciding what needs to happen and leaving a useful record of the result.
Proposed scope · concept illustration. Review evidence and availability.
Calm, exact, technical, trustworthy, and direct
Dayrook is the product and website brand operated by RadiantOS, the operator identified in the published legal documents. This site describes proposed scope and evaluation material; confirm the current release and commercial offer through the evidence register.
Mission, operating principles, and accountability
Why Dayrook exists.
Give MSPs one calm workspace to see every client's state, understand impact, take the right action, and retain evidence that the work is complete.Customer authority stays explicit
The customer chooses data placement, connected providers, operational policy, roles, approvals, AI provider, model, autonomy, and authorized operators.
Accountability follows the workflow
Ownership, scope, decision, action, result, failure, recovery, and customer-facing proof remain attached instead of being reconstructed later.
Try this in your evaluation
One connected client journey
Illustrative scenario · use it to plan a test, not as proof of a result
Fictional journey: a test device alerts, a ticket retains client context, an approved action runs and a reviewer checks the outcome before closing the ticket.
Define a successful result
Check these support boundaries
- Client identity and permissions
- Signal, ticket and proposed action
- Approval or policy authorization
- Outcome evidence and commercial scope
Acceptance record
Require matching client/resource IDs, authority, actor, action result and post-action observation across each handoff. Compare the included scope and provider connection record with the written offer.
Limits to resolve
This is a concept evaluation, not a recording of a supported production journey. Preapproved policy can authorize a bounded action; an exceptional action needs approval at the time of execution.
Questions, answered
About Dayrook: common questions
Who is Dayrook built for?
Dayrook is designed for modern MSPs managing complex, multi-client operations, with workflows for owners, service managers, technicians, security and specialist teams, administrators, and customer participants.
What makes Dayrook different from a tool bundle?
The platform connects shared context, authority, execution, proof, and reporting across modules instead of placing unrelated products behind one login.
How does Dayrook approach security and compliance?
Security controls live in the workflow through identity, tenant and region boundaries, least privilege, approvals, signed execution, audit, recovery, and evidence. Readiness is described precisely; certification is never implied without external confirmation.