- What Is an Inference Engine? What sits between a trained model and a served request.
- Deployment-Agnostic AI Infra. Why the tool should not dictate where your GPUs live.
- torch.compile() Performance Without the Warmup Penalty. Keeping the compiled speedup without paying for it on every cold start.
- How Python's Garbage Collection Works. Why the collector shows up in serving tail latency.
- GPU Sizing for LLM Inference: How Many Do You Need? Sizing the hardware the serving layer runs on.
One inference engine.
Any fine-tuned model.
NinetyFive is Numerata's inference layer: sub-50ms serving for models trained on your own data, deployed inside your own trust boundary. Trade signal generation is one thing teams build on it. It isn't the only one.
PART OF THE NUMERATA STACK · ninetyfive.gg ↗
CORE CAPABILITIES
Sub-50ms latency, for whatever you're serving.
CUSTOM MODEL SERVING
Serve models fine-tuned on your own data, not a generic public endpoint, so every response matches your domain, not someone else's.
SUB-50MS LATENCY
Built for real-time use cases: trading signals, risk scoring, chat and agents, anything where response time is part of the product experience.
PRIVATE BY DEFAULT
Runs inside your own infrastructure, private cloud or fully air-gapped. Fully offline local inference is coming soon.
BUILT FOR
The same low-latency layer, wherever you point it.
Real-time trade signal generation, scored on your own models, is proof this layer holds up under one of the tightest latency budgets we could find. Research assistants, compliance review agents, and client-facing chat run on the exact same serving path, just pointed at a different model.
YOUR DATA STAYS YOURS
Everything sent to NinetyFive is time-boxed, and never used to train any model except your own, critical when the data is trade or client data.
For code-based deployments specifically, binary files, anything covered by .gitignore, and files processed with git-crypt are excluded automatically. Teams that need more can run secure compute and secure training entirely within their own infrastructure, the same private-by-design posture behind every layer of Numerata's stack.
FURTHER READING
More on the serving layer.
GET STARTED