Deployment and sizing
How does this fit your infrastructure?
Choose where QCOS and QuantumLock run, size them, and leave with a brief your engineers, your security team and your procurement office can each read.
Step 1
Where does it run?
The deployment decides most of the contract, so it comes first.
Step 2
What goes in the stack?
Choose the modules and size them. Each answer changes the brief beside this form.
A sizing input for the conversation. It says nothing about any device.
Sealed evidence in QCOS Ledger comes with QCOS. All compute is reached through Softquantus Cloud.
Looking for SynapseX models? Seats and API volume for those are on the SynapseX LLM Console.
Step 3
Take the brief to your team
The panel is yours to keep. Save it as a PDF, email it to procurement, or send the link, which reopens this exact configuration. It holds no personal data.
Want performance rather than paperwork? Run the benchmarks on your own workload.
One brief, three readers
Written for the people who have to say yes
For the CTO
Which modules sit where, what connects to what, and which parts stay inside your boundary.
For the CISO
What the stack proves, what stays yours to prove, and the certifications we do not hold. All on one page.
For procurement
The licence lines by name and metric, and whether they are bought on the Platform or by proposal.