PHOSPHOR OPS
THE SHOP-FLOOR OS FOR NIGHT VISION BUILDERS
Not a CRM with your logo on it. A system built from how a night vision shop actually fails — undocumented tubes, mismatched channels, skipped purges, silent repair queues, and the ITAR shipment nobody double-checked — with a gate standing in front of every one of those mistakes.
IN PRODUCTION AT A WORKING NIGHT VISION SHOP
Built from how this business bleeds
Five failure modes every reseller-and-repair shop knows. Each one has a station standing in front of it.
A tube with no data sheet gets sold, and the warranty claim lands on you.
Every intensifier is vaulted by serial with its measured FOM, SNR, EBI, halo and blemish map. No sheet on file? The vault flags it unsellable until there is.
A bino ships with mismatched channels and comes back as a headache complaint.
The vault sorts by FOM so matched pairs are the default pull, and every build shows its channel spread before it ships.
A unit skips collimation or purge under deadline pressure and fogs on the first cold morning.
Five physical QC gates — collimation, purge, diopter, gain, blemish — and the build cannot advance until the bench signs off. The attempt to skip gets logged.
"Nobody told me anything" — the #1 complaint in this industry isn't slow repairs, it's silence.
Every RMA carries a promise date and an SLA clock, the bay computes your real median turnaround from closed jobs, and every job has a customer-ready status line to read down the phone.
One shipment to an unverified buyer is a $1M-per-violation ITAR problem.
Nothing controlled advances to Shipped unless the buyer's US-person attestation is on file and current. Foreign ship-to blocks regardless. The gate shows the cash value of work it's holding — so compliance gets chased, not skipped.
Every station, one system
Serialized intensifiers with full measured specs and provenance
Nine-stage kanban from intake to shipped, QC-gated
RMAs with promise dates and honest turnaround math
High-ticket deals with next actions that surface when due
Attestation registry and a ship-block that can't be talked around
Every fielded unit, its clock, and who to call before coverage lapses
Phone, tablet, bench computer — same system, one tap between stations. Three phosphor modes (P43 green, white, amber) so it looks like the tubes you sell.
Security is the product
You sell controlled articles. Your operations system should act like it knows that.
- ▸US-hosted, US-region compute and data — stated, not accidental
- ▸Seat-based access issued by your admin. No public sign-up exists
- ▸Every mutation re-checks the caller's role server-side — read-only means read-only
- ▸A full audit trail: who moved what, when, on every build, tube and RMA
- ▸Passphrases hashed (scrypt), sessions server-side; invites are single-use claim links — credentials never travel by email
- ▸Your data is yours: full CSV export of every book, any time, no asking
- ▸24/7 uptime monitoring with alerting — a human knows before you do
- ▸Point-in-time database recovery plus nightly off-site backups
- ▸Two-factor authentication for every seat
- ▸One isolated database per client — your data never shares a table with anyone
Listed separately on purpose: what's running is stated as running, what's contractual is stated as contractual. That's how we'd like to be sold to, too.
One flat monthly license: the platform, hosting, monitored uptime, upgrades, backups, and support — seats for your whole crew. Your data lives in its own isolated database, exportable in full at any time. You never touch a server, and you're never locked in.