Deliniext Files
Canonical file identity, dual representation, lifecycle processing, and multi-surface access for humans and agents.
Product line
Deliniext is built for enterprises that treat files as a system of record, then extend that record into security and machine intelligence without stitching a second control plane.
Each product is sold with a clear ideal and realization. Together they share identity, policy, audit, and deployment postures — SaaS, API-first, or self-hosted.
Canonical file identity, dual representation, lifecycle processing, and multi-surface access for humans and agents.
Native virus scanning and detection infrastructure for arbitrary formats and sizes, in the Files ledger or as its own plane.
Inference, classification, clustering, and segmentation on infrastructure you control; provisioned against the files you already govern.
Deliniext Files
Deliniext Files is enterprise file infrastructure: storage, versioning, processing, search, and policy in one ledger. Structured for agents. Valued for people. Not a consumer drive, and not an object-store wrapper with a chatbot taped on.
Every file carries a dual representation; a differential agents can parse, and a dossier operators can defend in an audit. Virus and PII events, retention, classification, and access control are bound to the record, not exported into a quarterly spreadsheet. SDK, MCP, tool calls, and the dashboard share the same guarantees, so platform teams do not rebuild a replica per audience.
Deliniext Virus Utilities
Deliniext Virus Utilities is our virus scanning and detection infrastructure: a security plane designed for files of any practical size and format, for individual operators and for enterprise fleets. Scanning is a lifecycle event with an audit trail, not an after-the-fact export you remember in Q4.
Enterprises already mix cloud-native detectors, open engines, and commercial suites. We treat that as a coverage problem, not a brand loyalty test. Virus Utilities aggregates complementary scanners and detection signals including industry engines such as ClamAV-class open tooling and commercial stacks, plus cloud-native pipelines so a single policy can demand a clean result before a write is committed, a version is pinned, or a training set is released.
When you run it with Deliniext Files, Harbor Scan events land on the same ledger humans and agents already trust. When you run it as a dedicated plane, the same scanning contract can sit in front of existing object stores and ingestion paths. The goal is operational: broad format coverage, large-object support, and a miss-intolerant posture you can put in a security review.
Deliniext ML Inference
Deliniext ML Inference is the MLScale offering: inference, classification, clustering, and segmentation on infrastructure you own or reserve. Deliniext is an enterprise intelligence company with a file-intelligence core. That core is what makes 10 TB-and-beyond checkpoints tractable instead of a weekend of copy jobs.
Most inference platforms assume the hard part is GPUs. For regulated and research enterprises, the hard part is the corpus: versions, scans, ACLs, and lineage that must survive the model. ML Inference sits on Deliniext Files so you can pin a clean, classified collection, provision a checkpoint, and run work without a shadow copy that legal never cleared.
Buy one product. Extend when the next plane has a named owner. The API does not fork when you add security or inference.
Identity, versions, policy, search, and surfaces. The ledger every other product writes back to.
Scanning and detection before commit, pin, or release — including corpora destined for training.
Inference and pipelines on collections that already have lineage, ACL, and a clean scan.
Humans and agents see the same events. Procurement chooses SaaS, API-first, or self-hosted.
The product does not change when the deployment does. Controls, intelligence, and APIs stay aligned across Files, Virus Utilities, and ML Inference.
SaaS
Restora operates the plane. You operate policy, agents, and teams.
API-first
Embed Deliniext behind your product. Files remain a system of record, not a hidden bucket.
Self-hosted
Run in your perimeter when regulation or latency will not leave the building.
Procurement