Customer files are sensitive
Drawings, CAD, specifications, and supplier prices should not move into an unrelated cloud by default.
On-premise manufacturing quoting
Keep sensitive RFQ files under shop control.
RapidRFQ is local-first manufacturing quoting software with shop-controlled files, SQLite data, users, backups, portals, and integration APIs.
Deployment reality
Shop control still has to be practical to operate.
Small shops need operable software
A product that requires a platform team, container cluster, or complex database is not practical for many estimators.
Local cannot mean trapped
The shop still needs intake, customer decisions, supplier responses, catalog data, and ERP handoff.
01 / 03
A simple shop-owned deployment boundary
The backend is a self-contained .NET service with a local SQLite database and file storage. Operational data remains under the installation data directory, with local user roles and explicit backup and restore workflows.
A Windows packaging path bundles the application and its private geometry runtime. Clean-machine qualification and signing remain required before broad unattended Windows distribution; paid pilots are configured and qualified for the target environment.
- Self-contained service
- Local SQLite and uploads
- Local accounts and roles
- Backup validation and restore
02 / 03
Expose only the workflows you choose
A reverse proxy can publish the marketing site, customer intake, signed quote links, and signed supplier response links on the shop's controlled hostname. The estimator workspace remains authenticated.
Portal tokens are bound to the relevant RFQ and commercial state. Browser sessions use server-held, HttpOnly cookies, and public write routes have upload limits, file-signature checks, and rate limiting.
- Authenticated estimator workspace
- Signed customer and supplier links
- Upload validation
- Public-route rate limits
03 / 03
Connect without surrendering the system of record
A versioned quote API exposes a deliberately narrow projection for shop-owned adapters. Catalog connectors can cache validated material and purchased-component offers with visible source, retrieval, expiry, MOQ, and availability.
These capabilities create a controlled integration boundary. They are not a claim that every ERP or distributor is already certified; target-specific adapters and credentials are qualified with the pilot shop.
- Versioned quote API
- Vendor-neutral catalogs
- Last-known-good cache behavior
- Target-specific adapter qualification
Straight answers
What a shop-controlled installation requires.
Is RapidRFQ cloud software?
It is local-first and can run on shop-controlled infrastructure. Public portals can still be exposed through the shop's own domain.
Does local deployment make it compliant by itself?
No. Local controls do not by themselves constitute CMMC, ITAR, SOC 2, or another certification.
Does it require Docker?
The pilot package runs as a self-contained service and does not require a container platform.
Review the boundary
Fit the installation to your actual shop environment.
Walk through target Windows or server hardware, users, file storage, network exposure, backups, portals, and support responsibilities.