Model the topology
Represent hosts, processors, cores, VMs, Windows editions, SQL workloads, CAL populations, and passive recovery roles.
Windows Server 2025 · SQL Server 2025Tell us what needs to run.
Tell us what needs to run.
See the server model take shape.
You do not need to know when to add a physical server, whether SQL belongs in a VM, or how many cores to enter. Start with the workloads, users, and resilience you understand. Review the proposed design before it changes the calculator.
Why TemenTemen keeps deterministic licensing math, official rule sources, visible assumptions, Debbie guidance, live products, and specialist validation in one path.Why nowA server design, virtualization decision, or agreement assumption can change the required license position before hardware, renewal, or migration commitments are made.
Deterministic mathAI never invents the quantityOfficial sourcesRules and assumptions stay visibleHuman validationAgreement-sensitive decisions are flagged
PHYSICAL CORESVIRTUAL CORESSTANDARD VS DATACENTERSERVER + CALHA AND DRSOFTWARE ASSURANCE
Plain language first
Answer what you know. Review what Temen recommends.
Workloads, placement, hardware, and resilience shape the topology. Organization, agreement, and access boundaries shape eligibility and license quantities, but they never silently add servers.
CALCULATOR SCOPEWindows Server and SQL ServerChange product scope
Advanced starting pointsChange the product scope
WINWindows ServerCores, editions, VMs, CALs, and RDSSQLSQL ServerCore, Server plus CAL, HA, and DRWIN + SQLCombinedCalculate both product families togetherUse the combined model when SQL runs on Windows Server and both product families must be calculated together.
What are you trying to estimate?
Choose the real-world task. You will see one question at a time, a live infrastructure preview, and a licensing result with any conditions clearly identified.
Prefer to describe the environment?Debbie can turn plain language into one complete proposal. You approve it before any setting changes.
What the calculator doesMake the rule inspectable.
Make the rule inspectable.
Keep the decision accountable.
The result is designed for planning and buying conversations. Microsoft Product Terms and the applicable agreement remain authoritative.
Apply the rules
Calculate minimums, stacking, per-VM eligibility, virtualization rights, and access requirements without asking an AI to perform the math.
Compare the paths
Expose alternatives where edition, licensing model, mobility, growth, or operational simplicity changes the decision.
Validate the purchase
Map approved live products, block unsafe self-service paths, and carry the complete context to a Temen licensing specialist.
NEED A REVIEWED DESIGN?
Talk to a licensing specialist