Host as one service
Run a single image behind a local endpoint. Your application sends only delta inputs and receives recomputed outputs.
docker run -p 8080:8080 hst-service:stable
Contact
Book a discovery call now.
Share the system shape, the update stream, and where you want HST deployed so we can map your fit quickly.
What we need before the call
Send these inputs and we can scope your evaluation fast.
Use a short memo or point us to existing notes.
- Workload shape — data size, update pattern, locality, and expected burst behavior.
- What must stay exact — any constraints where approximation is not acceptable.
- Current performance goals — latency target, throughput pressure, and fallback tolerance.
- System interfaces — what calls HST will wrap and expected request/response format.
- Deployment shape — bare VM, compose, Kubernetes, or existing REST gateway.
Deployment
How the solution is deployed in practice.
Most teams start with a single containerized service, then move to stack-native or orchestrated deployment once confidence is established.
Plug into existing compose or runtime
Deploy beside your service in the same network and route expensive calls through HST without changing core business logic.
image: ghcr.io/hornesci/hst-service:stable
Scale with your platform
Publish to your registry and run via your normal Helm, ECS, or Kubernetes flow with standard health checks and observability.
helm install hst ./chart --set image.tag=stable
In production, secrets and licensing are provided by your existing secret manager. HST runs inside your boundary and does not call home during runtime.
Direct contact
admin@hornesci.com (786) 720-9554