Evaluating Srasta
I need to know whether it fits
Choose one workflow, define evidence, and check the published deployment profiles before committing to a trial or pilot.
Documentation
Srasta touches evaluation, security, inference, knowledge, licensing, and operations. This hub is organized by the job you are trying to do, not by internal product area.
Choose A Path
Evaluating Srasta
Choose one workflow, define evidence, and check the published deployment profiles before committing to a trial or pilot.
Security Review
Use the architecture, security model, and public assurance documents to review data flow, controls, auditability, and SOC 2 posture.
Operating Srasta
Check the supported profile first, then use the installation, licensing, and operator guides for that configuration.
Start & Prove
For prospects, sponsors, and teams deciding whether Srasta solves a real workflow.
Choose a knowledge, coding, or application workflow; distinguish the model from its client; and review the full data path.
Open doc → Free checklistSix checks for a representative test set, data boundaries, exact configuration, operations, and a decision gate. No email required.
Open doc → PilotPlan one measurable workflow, name decision owners, collect reviewable evidence, and decide whether to stop, revise, or expand.
Open doc →Architecture & Governance
For security, platform, and architecture reviewers who need to understand the control model.
Customer perimeter, trust boundaries, services, data locations, outbound channels, and failure behavior.
Open doc → SecurityGateway enforcement, identity and RBAC, model access, tool policy, audit integrity, provenance, and telemetry boundaries.
Open doc → InferenceSupported deployment profiles, vLLM and MLX runtimes, governed model routes, model-fit decisions, and parser contracts.
Open doc → KnowledgeAuthenticated ingest, chunking, embeddings, sparse vectors, Milvus, workspace tagging, retrieval, reranking, and audit.
Open doc →Deploy & Operate
For operators planning infrastructure, licensing, health checks, recovery, and day-2 operations.
See the current public hardware and runtime matrix, validation status, and limits before planning an install.
Open doc → InstallerReview the installer flow and prerequisites after confirming that your hardware matches a supported profile.
Open doc → Planning referenceCompare operating shapes. Multi-host, Kubernetes, and HA/DR are design options, not published supported profiles today.
Open doc → LicensingTrial issuance, signed JWT entitlements, offline validation, expiry, grace, renewal, revocation, node-cap signals, and CRM handoff.
Open doc → OperationsRuntime health, drift, verify, self-heal, users, roles, audit review, upgrades, rollback, backups, restore, and support bundles.
Open doc →Planned, not available today
These concepts can inform a requirements conversation. They are not prerequisites for evaluating the current platform, and no release timing is committed.
Planned approach to connecting workflow outcomes and feedback to improvement decisions.
Explore the concept → RoadmapPlanned permission-aware memory for durable context; not available today.
Explore the concept → RoadmapPlanned tools for teams building their own agents. Scope and timing remain open.
Explore the direction →Security review
These maintained pages explain the public posture. Ask for current controls evidence or a questionnaire response matched to your review.
Get Help
Use the installation and operator guides for supported configurations, setup steps, health checks, and recovery.
Open installation guide →Use Discord for public, non-sensitive setup questions and shared troubleshooting. Community support is best effort.
Join Srasta Community support →Use email for account, licensing, security, pilot, paid-support, or other private matters.
Email [email protected] →Never post license keys, credentials, customer data, confidential code or documents, or logs containing secrets in Discord.