Intelligence
Decisions you can inspect.
The optimisation and scheduling layer that explains why one eligible region or provider should win over another.
System view
- Hard constraints
- Filter
- Policy factors
- Score
- Decision output
- Rank + rationale
Change the objective. Read the result.
Each objective changes factor weights, eligibility and the final ranking. Rejected regions remain visible so the outcome is understandable.
Policy demo. Candidate regions, scores and conclusions use illustrative data and do not represent a current FabriX production decision.
No single axis dominates. The scheduler trades cost against latency and carbon until the marginal gain on each is equal.
- Cost
- 24%
- Latency
- 24%
- Carbon
- 20%
- Availability
- 22%
- Residency
- 10%
- Paris0.70
- Stockholm0.69
- Virginia0.67
- Frankfurt0.61
- Warsaw0.53
- London0.49
- Dublin0.36
- Dubai0.36
Paris clears every constraint at once: 6 ms, $2.19/hr and 56 g/kWh with headroom to grow.
Paris is selected for the balanced objective. Paris clears every constraint at once: 6 ms, $2.19/hr and 56 g/kWh with headroom to grow.
A decision is a set of trade-offs.
Some inputs are hard constraints. Others contribute to a score. The policy should make that distinction visible.
Cost
Compare the modelled price of eligible allocations, including the effect of region and contract term.
Latency
Prefer regions that keep the request inside its network latency limit.
Accelerator type
Reject supply that does not match the required architecture, memory profile or interconnect.
Availability
Score capacity against the requested quantity and the operational state of each region.
Energy and carbon
Use electricity price, renewable share and carbon intensity when the workload can move in time or geography.
Sovereignty and compliance
Filter out locations that do not satisfy residency, jurisdiction or compliance policy.
Resilience
Prefer allocations that can tolerate endpoint or provider failure when continuity matters more than price.
Bring your placement policy.
Tell FabriX which technical, geographic and commercial inputs should govern your compute requests.