Access & governance
Identity, purpose, policy, quota and approval enter before model execution.
Reference architecture and planning economics
A transparent starting point for running strong open-weight language models inside an organization's own trust boundary—with architecture, capacity and cost assumptions exposed.
01 / Reference architecture
The durable system is not the GPU server alone. It is the governed path around models, data and human authority.
Identity, purpose, policy, quota and approval enter before model execution.
Gateway, router, model registry, evaluation gates and release policy stay separate from models.
Retrieval, object storage and tools inherit source authority and remain network-bounded.
Open-weight models run in isolated pools with quantization, batching and task-aware routing.
Tracing, quality evaluation, power telemetry and human review shape every release.
02 / Capacity scenarios
Memory fit depends on model architecture, precision, context length, concurrency and serving software. Benchmark before purchase.
Evaluation, retrieval, fine-tuning experiments and controlled team use
Shared inference, higher concurrency, governed tools and service resilience
Multiple model services, large-context research and capacity expansion
Reference prices include accelerator hardware, host platform, ECC memory, NVMe storage, network/security components and an integration contingency. They are planning estimates—not vendor quotes.
03 / Türkiye landed cost
Confirm GTIP classification, origin, trade regime, Incoterm and any additional duty with a licensed customs broker before ordering.
Import VAT is shown in gross cash outlay. Whether it is recoverable depends on the taxpayer and use; obtain tax advice.
Refresh accelerator prices, supplier quote, TCMB selling rate, freight, tariff and VAT—and always recalculate on the customs declaration date.
04 / Sustainable operation
Sustainability begins with routing and measurement—not a larger server.
Prefer the smallest path that meets the evaluated quality threshold.
Track energy, utilization, queue time and accepted output by workload.
Use batching, quotas and isolated pools before adding hardware.
Sources & method
Method: reference CapEx × freight/insurance = CIF; customs duty is applied to CIF; import VAT is applied to CIF plus duty; the clearance allowance is added separately. This simplified public model excludes financing, KKDF, local reseller margin, building works, electricity and recoverability timing.
Manifesto & rationale
The thinking behind the system
Open-weight models make it possible to inspect the model artifact, choose the serving stack, control the network path and keep sensitive context inside an accountable environment. Local operation is not automatically secure or economical, however. The surrounding architecture determines whether permissions, evidence, updates and human authority survive real use.
Project PULSAR treats hardware as one replaceable layer inside a larger operating model. Identity, policy, routing, permitted context, evaluation, observability and release governance must remain stable while accelerators and models evolve.
The reference systems on this page are not product bundles or procurement recommendations. They are public research envelopes for comparing:
The starting assumption uses 96 GB professional server accelerators because this creates a useful, modular memory unit for open-weight inference. Equivalent accelerators and future architectures should be compared against the same workload and governance tests.
Reference CapEx is expressed in USD and includes the accelerator set, host platform, ECC memory, local NVMe, network/security components and an integration contingency. It excludes building works, financing, electricity, local reseller margin and contractual support unless stated.
For Türkiye, the calculator separates net landed cost excluding import VAT from gross cash outlay including import VAT. A 0% customs-duty input is only a planning default. Classification, origin and the current import regime must be confirmed before every order.
Prices, tax rates and exchange rates expire. Record the calculation date, refresh the assumptions at least monthly and recalculate using the official exchange rate and tariff position on the customs declaration date.
Do not buy the largest system that fits the budget. Select a small set of representative workloads, establish quality and latency thresholds, measure the smallest viable configuration and preserve an expansion path. Capacity earns its place through accepted output—not theoretical model size.