Storage & File Management
Keep the right records accessible for as long as they are needed.
Review how backup artifacts, documents, recordings and exports are stored and retrieved. Plan permissions, retention and recovery together so access and deletion decisions are clear.
Start with the recovery decision
What needs to come back?
Link each object to its customer, source workflow, region, class, owner, retention, and audit state.
Separate versioned Object Lock storage where policy requires it
Dayrook workers and signed access flows
Storage management
Regional object identity, access, retention, hold, and lifecycle evidenceArtifact lifecycleRegional policy
01Store
BoundRegion and source attached
02Retain
AppliedClass, hold, and expiry
03Access
ControlledShort-lived permission
04Delete
Not duePolicy and recovery checked
Illustrative workflow · explore the steps · no action is executed
01
Create in the right region
Classify the artifact, assign tenant and customer ownership, and place it in the approved regional storage class.
Confirm this step for your release, permissions and environment.02
Use through governed access
Authorize a short-lived signed upload or download and record the related user, workflow, object, and expiration.
Confirm this step for your release, permissions and environment.03
Apply lifecycle policy
Evaluate retention, archive state, legal hold, Object Lock, export, and deletion eligibility before any transition.
Confirm this step for your release, permissions and environment.Keep operational files findable without losing region, retention, or authority.
Use short-lived signed access, lifecycle jobs, legal hold, usage, and recovery state instead of durable exposure.
Inside the workflow
The work this connects.
- Contextual file browser
- Browse authorized artifacts by tenant, customer, service, object type, owner, date, region, and linked work record.
- Version and revision history
- Track document and artifact versions without losing provenance or linked audit state.
- Short-lived signed access
- Grant bounded uploads, downloads, and approved external shares without exposing durable storage credentials.
- Retention and legal hold
- Drive archive, prune, purge, deletion, and hold behavior from central tenant-aware policy.
- Usage and quotas
- Measure storage by tenant, customer, service, artifact class, region, and billing meter.
- Cross-artifact search
- Search governed metadata and permitted indexes across operational documents, exports, reports, and recovery records.
Try one useful scenario
Archive retrieval and a revoked link
Fictional example: an archived recovery artifact is requested under an approved hold. Retrieval stays pending until ready; a previously shared link is tested after its authorization changes. A preservation hold can prevent deletion without granting restore access. Application hold and storage-enforced Object Lock are distinct controls; require evidence for the one relied on. Record requested, retrieving, ready, failed and expired states, then test whether an issued signed URL remains usable until expiry after access changes.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Record storage tier, hold authority, retrieval wait, expiry, access result, deletion eligibility and offboarding owner.
Get the evaluation worksheet →Check the support boundaries
- Document versus recovery-artifact access tiers
- Application hold versus storage Object Lock
- Deletion eligibility, legal holds and offboarding
- Signed-link expiry and sharing authorization
Application flags do not prove storage-enforced Object Lock. A signed URL may remain usable until expiry depending on implementation; verify it. Confirm retained-storage, retrieval and egress charges.
Check public evidence and availability →Scope, availability and evaluation details
Archive-backed objects can require queued retrieval or prewarming.
Active retention and legal hold can block pruning, purge, offboarding deletion, or other destructive work.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
One regional artifact layer
Backups, recordings, reports, exports, and documents use tenant-bound metadata with selected-region Vultr Archival Object Storage; retention-locked data uses its separate approved versioned class.
Access returns to the source workflow
Short-lived signed uploads and downloads link each artifact to its customer, device, ticket, report, backup, or evidence record without exposing durable storage credentials.
Backup, recording, reporting, export, documentation, audit, legal hold, and billing owners share one regional artifact contract.
Questions, answered
Before you choose your next step.
Where does Dayrook store object artifacts?
Ordinary artifacts use regional Vultr Archival Object Storage. Data requiring versioned Object Lock uses a separate regional storage class.
Can files be shared externally?
Authorized workflows can issue short-lived signed links with expiry and audit. Public durable object URLs are not used.
Does legal hold stop deletion?
Target design: An active legal hold is evaluated before lifecycle purge, pruning, offboarding deletion, or other destructive storage work.
Can customers see storage usage?
Target design: Governed usage and quota views can be broken down by tenant, customer, service, class, and region.