Teams need exposure and outcome joins, not only offline scores detached from serving behavior.
Self-hosted recommendation infrastructure
Recommendations you can evaluate, ship, and roll back.
RecSys gives technical and commercial teams a concrete path from first recommendation request to credible evaluation evidence and controlled production rollout.
Ready: config, rules, artifact manifest
Problem
Recommendation systems fail when teams cannot explain the rollout.
RecSys treats config, rules, and artifact manifests as operational rollback levers.
Docs, pricing, licensing, security posture, and evaluation paths are explicit from the start.
System
One suite for serving, pipelines, evaluation, and audit trails.
- recsys-service: HTTP recommendation API, admin config/rules, auth, and exposure logging.
- recsys-algo: deterministic ranking, blending, personalization, rules, and diversity controls.
- recsys-pipelines: offline jobs that publish versioned artifacts and current manifests.
- recsys-eval: Apache-2.0 evaluation CLI for offline gates, experiments, OPE, and reports.
Evaluation
Ship, hold, or roll back with a decision record.
The evaluation loop starts with schemas and join integrity, then checks guardrails and business metrics before rollout.
Exposure, outcome, assignment, report, and manifest schemas are checked before interpretation.
Error rate, latency, empty recommendations, and warning rates stay visible during rollout.
Config, rules, and manifest versions remain part of the release record.
Pricing
Start with a commercial evaluation or choose a production scope.
30 days, 1 tenant, 1 deployment, non-production evaluation.
Ask about this plan1 tenant, 1 production deployment, up to 2 non-prod environments, 1-2 production surfaces.
Ask about this planUp to 3 tenants and/or deployments, up to 6 production recommendation surfaces.
Ask about this planCustom scope for OEM, regulated deployments, multi-region HA, custom SLA, or legal/security terms.
Discuss scopeProof
The documentation stays technical and inspectable.
Next step
Evaluate RecSys with a focused pilot.
Start with a commercial evaluation, inspect the technical docs, or open a commercial licensing discussion when procurement needs a clearer path.