Dedicated server hosting is an allocation problem. A customer orders a server with specific specs — a particular CPU, a certain amount of RAM, a storage configuration — and your team needs to find a physical machine in your inventory that matches. When you have an exact match available, it's straightforward. But hardware rarely comes in perfectly uniform configurations, and that's where equivalences come in.
The Problem: Rigid Matching Wastes Inventory
Consider a common scenario. A customer orders a server with 500GB SSDs. You have 20 servers in stock, but they have 480GB SSDs — a standard enterprise drive size that's functionally identical. Without an equivalence system, those servers don't match the order, and they sit idle while you wait for exact-match hardware.
The same problem applies to CPUs. A customer orders an "Intel Xeon E5-2690." You have servers with the E5-2690 v3 and E5-2690 v4 — both in the same family, both meeting the performance requirements. A rigid string-match allocation system wouldn't consider these valid options.
Manually handling these cases — checking each order against available inventory, making judgment calls about compatibility — doesn't scale. It wastes your team's time and leaves hardware underutilized.
How Equivalences Solve This
An equivalence system lets you define rules that map one hardware spec to another, telling the allocation engine: "these are interchangeable." FluxBilling includes two parallel equivalence engines — one for CPUs and one for storage — that run automatically during server allocation.
CPU Equivalences
CPU equivalences work on pattern matching. You define pairs of CPU patterns that should be treated as compatible:
- "Intel Xeon E5-2690" is equivalent to "Intel Xeon E5-2690 v3"
- "Intel Xeon E5-2690" is equivalent to "Intel Xeon E5-2690 v4"
- "AMD EPYC 7742" is equivalent to "AMD EPYC 7763"
When the allocation engine evaluates a server against an order, it normalizes both the required CPU and the server's CPU — stripping trademark symbols, frequency notations, and formatting noise — then applies your equivalence rules. If the normalized patterns match (directly or through an equivalence), the server is considered compatible.
The matching is smart about CPU counts too. It understands "Dual," "2x," "Quad," "4x" and other common formats, so "Dual Xeon E5-2690 v3" correctly matches a requirement for a dual-CPU server.
Storage Equivalences
Storage equivalences work on numeric sizes with optional type constraints. You define mappings like:
- 480GB is equivalent to 500GB (for SSDs)
- 960GB is equivalent to 1000GB (for SSDs)
- 1920GB is equivalent to 2000GB (for NVMe)
- 3840GB is equivalent to 4000GB (for any type)
These mappings account for the reality that enterprise drive manufacturers use different size conventions. A 480GB SSD and a 500GB SSD are functionally the same tier of storage, and your customers won't notice the difference.
Storage equivalences support type-specific rules. You can create a mapping that only applies to SSDs, only to NVMe, or only to HDDs. If you create a mapping without a storage type, it applies universally. Type-specific mappings take precedence over universal ones.
How It Works During Allocation
When a customer places an order for a dedicated server, FluxBilling's allocation engine runs a series of modules against your available inventory. Here's what happens with equivalences:
- Load available servers — the engine queries all servers with "available" status
- Run CPU compatibility module — loads active CPU equivalences from the database, normalizes CPU strings on both sides, applies equivalence mappings, and scores each server (0-100) based on how well its CPU matches the requirement
- Run storage availability module — loads active storage equivalences, parses disk configurations (understanding formats like "2x 480GB SSD" or "4x 1.92TB NVMe"), applies equivalence mappings to normalize sizes, and scores based on capacity match
- Aggregate scores — servers are ranked by their combined compatibility score across all modules
- Present results — your team sees a ranked list of matching servers with detailed scores and match reasoning
Scoring
Not all matches are equal. The allocation engine assigns scores to reflect match quality:
- 100 — exact match (within 5% tolerance)
- 95 — slightly over-specced (e.g., 1TB drive for a 500GB requirement)
- 90 — significantly over-specced
- 85 — large overage
- 0 — no match
This lets your team make informed decisions. A score of 100 means you have a perfect match. A score of 90 means the server works but you're giving the customer more than they're paying for — which might be fine for retention, or might be wasteful depending on your inventory levels.
Managing Equivalences
Equivalences are managed through the admin panel under the Allocation section. The interface provides:
- Create — add new equivalence rules with patterns (CPU) or sizes (storage)
- Edit — modify existing mappings
- Toggle — temporarily disable an equivalence without deleting it (useful for testing)
- Delete — remove rules that are no longer relevant
Each equivalence has an active/inactive flag, so you can experiment with new mappings without committing to them. Disabled equivalences are excluded from the allocation engine entirely.
Why This Matters for Your Business
The equivalence system directly impacts your bottom line in three ways:
1. Higher Inventory Utilization
Without equivalences, servers with 480GB drives can't fill orders for 500GB drives, even though they're functionally identical. With equivalences, those servers are available for allocation. More of your hardware generates revenue instead of sitting idle.
2. Faster Fulfillment
Manual hardware matching — comparing order specs against available inventory, making case-by-case compatibility judgments — takes time. An automated system with equivalence rules handles this instantly, reducing the time between order placement and provisioning.
3. Fewer Procurement Mistakes
When your allocation engine understands that 480GB and 500GB SSDs are interchangeable, you don't need to maintain exact-match stock for every possible configuration. You can standardize on fewer hardware SKUs and let the equivalence system handle the mapping.
Getting Started
If you're running a dedicated server hosting business, setting up equivalences is one of the quickest wins for operational efficiency. Start by mapping the common drive size discrepancies in your inventory (480↔500, 960↔1000, 1920↔2000), then add CPU family equivalences for the processor lines you stock.
FluxBilling includes the full allocation engine with CPU and storage equivalences in every plan. Explore the full feature set to see how smart allocation fits into the broader platform, or check out pricing to get started.
