PC Builder
Spec a custom PC — processor, graphics, memory, storage — with real compatibility rules and a live running price.
Open the PC Builder demoThe configurator for made-to-order manufacturers
If your customers choose from options — sizes, materials, add-ons, packages — every combination has its own rules and its own price. xtconfig lets your team change those rules and prices themselves, publish safely, and drop a fast, accurate configurator straight onto your website — with a quote the customer can’t fudge and you can bank on.
Every published price is recomputed and verified on the server — the number a customer sees is a number you can honor.
Three real catalogs on the same engine — every option, rule, and price below is computed live from a published catalog version, exactly as it would be on your site.
Spec a custom PC — processor, graphics, memory, storage — with real compatibility rules and a live running price.
Open the PC Builder demoSize a cloud server: compute, storage, and network options that rule each other in and out, priced as you click.
Open the Cloud servers demoA playful catalog that shows the same engine driving recipe-style rules between components.
Open the Crafting recipes demoMost configurators fail in one of four expensive ways. You have probably lived at least two of them.
A pricing rule was off by a decimal, or two options combined that never should have. You honored a bad price or lost the customer's trust — either way it came out of your margin.
Updating a price or a compatibility rule means a ticket, a wait, and a deploy. Your catalog moves at the speed of your slowest engineer.
Slow, out of sync with what you can actually build, or a glorified brochure that hands the real work back to a salesperson on the phone.
Your rules, prices, and customer data live inside someone else's hosted product — on their terms, with their outages and their price hikes.
Every published price is recomputed and verified on the server from your own rules. The number a customer sees is a number you can honor.
Your catalog manager changes a price or a rule, previews it, and publishes — no developer, no deploy. A wrong change is one click to undo.
Fast, works offline, and shows only what you can actually build. It updates the moment you publish a new catalog version.
An optional AI copilot helps your team make catalog changes in plain language — it can only propose edits, never publish them.
Runs as an isolated deployment you control, with your data in one database you can back up and restore. No forced dependency on a hosted platform.
The engine's behavior is checked against a reference on every change; a pricing mistake fails an automated gate before it can reach a customer.
When you publish, xtconfig compiles your catalog and the configuration engine into a single tiny WebAssembly runtime — a self-contained package on the order of a couple hundred kilobytes that runs your exact pricing and availability rules anywhere: your website, a dealer or field-sales tool working offline, a showroom kiosk, a partner’s app. Availability and price compute instantly, on-device, with no round-trip — and the server still independently re-validates every final quote.
See the embed showcaseMade-to-order, not made-to-stock. Rules between the options. A price that must hold. If your salespeople quote from a spreadsheet, a binder, or their memory — that’s a configuration engine held together by one person. That’s what xtconfig replaces.
Configurator pricing is a fog on purpose — per-seat licenses, revenue-tiered subscriptions, and billable services for every rule change. xtconfig charges none of those taxes by design:
More salespeople, dealers, and locations using the configurator is the point — not a line item. Unlimited users on one deployment.
Your bill doesn’t climb because you grew. No revenue tiers, no per-quote metering, no per-embed charges.
Self-service editing, validation, and one-click publish are the product — the person who knows the price is the person who changes it. No services queue.
Yes — because the browser's price is never the one that counts. The server independently recomputes and validates every quote from your published rules. A tampered client gets caught.
Every change is previewed and validated against your own scenarios before it goes live, publishes as a single atomic version, and can be rolled back in one click.
No. The core configure-and-quote workflow runs with every optional integration switched off and no outbound calls. The copilot is a convenience you can enable or ignore.
Your catalog is imported as data, not rebuilt as code. Bringing on a new product line or vendor is an import and a review, not an engineering project.
The live demos run real published catalogs on the same engine your customers would use.