Riftline Private AI
For organizations ready to put approved company knowledge into a private, source-grounded workspace with managed deployment and support.
Discuss a Riftline Private AI deployment →Deployment & evaluation
Start with the workflow, boundary, and decision.
Zeah products have different entry points: managed private deployments, a downloadable commercial preview, controlled operational deployments, and live monitoring. Scoped evaluations still begin with a clear owner, boundary, and success criterion.
Current entry points
Choose the product that matches the work.
Riftline Migrate
For MSP and IT technicians who want to try a profile-aware Windows migration workflow. One completed user migration is free.
Start with Riftline Migrate →SentryVision
For operators prepared to qualify approved cameras, recording/history workflows, investigations, infrastructure health, and local review.
Discuss SentryVision fit →DomainGuard
For MSPs and security teams that need recurring external posture, remediation workflow, change history, webhooks, and client reporting.
Explore DomainGuard →Research partnerships
Riftline Spatial follows a separate research path.
Riftline Spatial is Zeah's primary research direction, not a generally available commercial product. Design partnerships focus on evidence models, spatial restrictions, confidence, and review workflows.
Review the research direction →Scoped deployment process
Five steps from problem to decision.
The process stays intentionally narrow so both sides can see what is useful, what needs work, and what a responsible next step requires.
Clarify the problem.
Identify the operator, current workflow, friction, environment, and decision the deployment or evaluation should inform.
Define the boundary.
Agree on approved inputs, users, deployment location, exclusions, and success criteria.
Set up the scoped environment.
Prepare the product, synthetic or approved evaluation data, access, and a safe test plan.
Review the results.
Test the workflow, measure usefulness, identify limits, and collect structured operator feedback.
Choose what follows.
Expand, adjust, pause, or stop. Expanding beyond the initial scope is a separate decision based on the results.
What the customer prepares
Context and ownership.
- A specific operational workflow
- A named internal pilot owner
- Approved source material, test devices, or synthetic data
- Known privacy and deployment constraints
- People available for review and feedback
- A decision the pilot can inform
What Zeah provides
Structure and evidence.
- Product-fit and boundary review
- A written pilot scope and exclusions
- Controlled configuration and demonstration plan
- Validation checkpoints
- Visible product limitations
- A closing review and recommended next step
Success criteria
Measure the workflow, not a vanity metric.
- UsefulnessDoes the product improve the defined operator task?
- QualityAre answers, events, or incidents reviewable and fit for the pilot purpose?
- BoundaryCan the agreed data, deployment, and access constraints be maintained?
- OperationsAre ownership, support needs, failure modes, and next steps clear?
Pricing and next steps
Scoped after discovery.
Pilot pricing depends on the workflow, environment, product stage, and validation plan. Moving beyond a pilot is a separate decision made after the results are reviewed.
Start with context