FAQ / SHORT ANSWERS, LINKED TO THE LONG ONES

Short answers. The long answer is one link away.

Every answer here restates something the site already says elsewhere — nothing new is claimed on this page.

What is 3D cartonization?

Deciding which items fit into which containers, and exactly where, in three dimensions — the problem Packvium solves as a request/response contract rather than a UI.

Which languages does Packvium support?

Python and PHP as reference engines, a Rust core with a stable C ABI, and a WebAssembly build for the browser. All four implement the same request contract independently, held to one conformance suite.

Is Packvium free and open source?

Yes — MIT licensed, across every package in the suite.

What shapes can it pack?

Rigid rectangular cuboids only. Irregular, deformable and cylindrical items are rejected explicitly rather than approximated; see the roadmap for what is planned.

Is the packing guaranteed optimal?

Not yet certified. 3D bin packing is NP-hard; Packvium runs a bounded search under an operation-counted budget and labels a result optimal only where a proof exists.

Is Packvium fast?

No speed claim is published yet. A fair cross-runtime speed frontier — cold and warm solve time, throughput, memory, on one pinned architecture — has not been measured across all four engines.

How do I know the benchmark numbers are trustworthy?

Every number on the benchmarks page is recomputed by an independent validator from the placements each engine actually returned, never taken from an engine's own self-report.

How do I get started?

Install the package for your runtime and send one request — see Getting started — or try a real request in the Playground first, without installing anything.

Can I add custom rules or scoring?

Yes, through five in-process extension points. A rule that must hold for every caller belongs in the request schema instead, so every engine and the validator enforce it the same way — see Extending an engine.

How do I report a bug, a security issue, or contribute?

A reproducible fixture is the most useful bug report — see Contribute. Report a security vulnerability privately — see Security — never through a public issue.