Operates without a connection
Scheduling, customer lookup, repair orders, payments, and printing all work offline. None of it depends on the Internet.
We build appliances, not subscriptions.
Systems that run on hardware you own, in your building, under your control — so your data is yours, you own it, and nobody else holds a copy. Software you depend on should not be something you rent, and what you store in it should never be something you need a vendor’s permission to keep.
Runs on hardware you own
It works when the Internet doesn’t
No recurring license fees
You own the software and the data
Products
Different problems, same answer.
Scissa solutions are built around local access and local data you control and own. They live on your network and keep working even when the Internet goes down — and because you own it, you don’t have to keep paying us to use it.
Available now
AutoShop
Shop management for independent auto repair. Scheduling, repair orders, invoicing, and payments on one machine on the shop’s shelf. Every bay tablet opens it in a browser.
Explore AutoShop → In developmentAutoSales
Everything a small used-car lot runs on: inventory and photos, deal desking, Texas title and plate work, and your listings pushed out to the classified sites — on one box on the lot instead of three monthly subscriptions.
Explore AutoSales → Available nowRedoubt
A private AI assistant that answers questions about your own documents — contracts, case files, project records. It runs on a box in your office and nothing you ask it ever leaves the building.
Explore Redoubt → In developmentScissa for Drivers
A free phone app that keeps a car’s full service history on its owner’s phone. Scan the QR on an AutoShop invoice and the visit is in their pocket — no account, no server, nothing for us to hold.
Explore the app →
Custom development
You have the idea. We build it.
Most of what we do starts as a sketch on the back of a napkin. We turn it into software that runs — and then we hand you the keys: the source, the infrastructure, the documentation, all of it.
Discovery that produces a decision
Not a deck. A written scope, a fixed number, and an honest read on whether you should build it at all.
A working prototype early
Something you can click by week three, because opinions about screenshots are worthless.
Handover as a deliverable
Documentation and a walkthrough are part of the build, not a favor at the end.
Privacy
You own your data. We do not get a copy.
Every other vendor in these categories holds your data on their servers and asks you to trust a policy. We took the other route and built the system so the question never comes up.
There is no data business here, because there is no data. We cannot sell,
mine, analyze, or train on your data — not because we promise not to, but because it lives on a machine in your building and we have no access to it.
Stays on your hardware · always
We never see it
- Your customers, and everything you know about them
- Your invoices, payments, and financial history
- Your documents and their contents
- Card numbers — these never enter the software at all
- Every record you have ever written
All we ever receive
And only this
- Which license is on which box
- Software version and whether the box is healthy
- An encrypted backup you hold the keys to. We cannot read it.
- A support session you turned on, which expires on its own. We have no access without your permission
- Nothing else, ever
No analytics on your content
No telemetry containing your text, no “anonymized” samples, no crash reports carrying customer records.
Your data is never a bargaining chip
Full-fidelity export at any time, whether or not you hold a current support plan. It was never leverage, so we never have to give it up.
Security patches are free, forever
To every system we have sold, regardless of support status. Staying patched shouldn’t require a subscription.
Every product follows the same three rules
If you stop paying us, it keeps working.
You buy a perpetual license. We do not build remote kill switches, and we never will. What lapses is support and updates — never access to your own information. Your data lives on your hardware, it works when the Internet doesn’t, and leaving is always your decision to make.
Own the data. Own the software. Own the machine.
Available now
AutoShop
Shop management for independent auto repair — one to eight bays. Scheduling, customers and vehicles, repair orders with per-line authorization, invoicing, payments, and customer texting.
For: owners paying $179–$2,000 a month for cloud shop software and tired of the increases.
Explore AutoShop → In developmentAutoSales
Dealership management for a small independent used-car lot — 20 to 100 units. Inventory and photos, cost basis and gross, deal desking, Texas titling and plate work, listing syndication, and your own website.
For: lots paying $190–$500 a month across a DMS, a website vendor and listing subscriptions — $11,000 to $30,000 over five years.
Explore AutoSales → Available nowRedoubt
A private AI assistant over your own documents. Ask a question in plain language, get an answer with a citation to the exact clause — from a machine on your network with no connection to the outside world.
For: firms whose confidentiality obligations make a cloud AI tool a non-starter — legal, accounting, healthcare, defense, engineering.
Explore Redoubt →
We only sell perpetual licenses. You buy the software once and it’s yours.
The machine it runs on is yours. The database on that machine is yours, and so is every record
inside it. Support and updates are a separate annual plan — let it lapse and everything
keeps running exactly as it did the day before, because neither product was built with a way to
turn it off.
Shop management software that runs in your shop.
A single computer in your back office runs the entire operation — front desk, bay tablets, and your phone. You own the hardware and the data on it, and the system keeps working even when you don’t have an Internet connection.
No Internet required
Card numbers never enter the software
Your database, on your machine
Front desk · the board Today — Tuesday · 7 open · 2 waiting
| RO | Vehicle | Customer | Tech | Status | Total |
|---|---|---|---|---|---|
| 1042 | 2019 F-150 | M. Alvarez | Ray | In progress | 650.51 |
| 1043 | 2016 Civic | Northside Plumbing | — | Waiting on parts | 1,284.00 |
| 1044 | 2021 Silverado | J. Whitfield | — | Needs approval | 2,190.40 |
| 1045 | 2014 Odyssey | P. Nguyen | Marco | Ready | 412.75 |
| 1047 | 2020 Escape | S. Boyd | — | Estimate sent | 318.60 |
Status is carried by both color and label — never color alone,
so it stays readable on a dirty screen and for color-blind staff.
Continuity
When the connection drops, the shop keeps running.
Most shop management systems run in a remote data center. If your Internet service fails — or the vendor’s does — the front desk stops. AutoShop runs on hardware in your building, so it doesn’t.
Reconnects automatically
Messages, parts orders, and backups queue while you’re offline and send once service returns. Nothing is lost and nothing is sent twice.
Responds immediately
There’s no round trip to a remote server. Customer history and parts lookups open without delay.
Ordering parts is the one function that requires a connection, since your supplier is online. You can still build the estimate, get approval, and complete the work — the order is sent once service returns.
What’s in the box
Every module. One price. Nothing held back for a higher tier.
This is the whole system, not a starter edition. There is no plan above this one, so there is nothing above this one to sell you later.
Customers & vehicles
A customer is a person or a business, and either can hold as many vehicles as they own. VIN decode, plate lookup, mileage history, and the complete service history on every vehicle.
Fleet & commercial accounts
Organization accounts with authorized drivers, PO numbers on the repair order, net-30 billing terms, monthly statements, and per-account pricing. Built into the customer model from day one, not bolted on.
Scheduling
Appointment calendar with bay and technician assignment, drop-off versus waiting, and no-show tracking.
Repair orders
Estimate through authorization, in progress, complete, invoiced. Line items for labor, parts, sublet, and fees, with notes and technician assignment on each.
Estimate authorization
Per line, not per document — by tablet signature, text reply, email, or verbally with the writer recording it. Snapshots exactly what was approved, and gates re-authorization at the Texas 10% line.
Canned jobs & labor
Shop-defined canned jobs and direct hour entry. An estimate can be completed with zero Internet — that is a permanent design choice, not a stopgap until an integration lands.
Parts inventory
On-hand tracking, cost against sale price, a markup matrix that sets sell prices automatically, and receiving.
Parts ordering
About 20,000 stores in one search — the national chains, WorldPac, dealers, and local jobbers. Your supplier accounts, your negotiated pricing, and we take no margin.
Invoicing
Repair order to invoice, with tax and discounts handled correctly. Append-only once issued — corrections are a credit or adjustment that references the original, the way books are supposed to work.
Payments
Card through your own processor (token only — numbers never enter the software), cash, check, and split payments across methods or across time.
Printing & documents
Estimates, repair orders, invoices, receipts, and statements to a real printer on your network, plus a PDF archive of every document you have ever issued.
Document branding
Your logo, address, license numbers, and your own wording per document type. Snapshotted onto each document when it is issued, so a reprint years later is identical to the original.
Customer delivery
A text summary with a pay link hosted by your processor, and an email carrying the PDF itself. No document of yours is ever hosted by us.
Reporting
Average repair order, gross profit split labor and parts, effective labor rate, technician efficiency, car count, and customer retention — computed the way the trade computes them.
Users & roles
Owner, manager, service writer, and technician. What a person may do is checked on the server for every single action, not hidden in the interface.
Data export
Your entire database in full fidelity, prominent in the interface rather than buried, and available regardless of whether any plan is current.
Backup & restore
Encrypted on the box before it goes anywhere, to our managed service or to storage you own. Weekly report by email, and a restore procedure that has actually been performed rather than merely documented.
Scissa for Drivers handoff
A QR code on every invoice that puts the customer’s service record on their phone. Nothing to sign up for, and nothing leaves your box to make it work.
Next release — already scoped
- Digital vehicle inspections — photo and video, red/yellow/green, sent to the customer for remote approval
- Two-way texting — status conversations, not just outbound notices
- QuickBooks Online sync — invoices and payments push across; QuickBooks stays your accounting source of truth
- ProDemand and ALLDATA labor times — from the subscription you already pay for
- Follow-up engine — declined work, service intervals, and satisfaction surveys on rules you set
Included with Care+. Not a paid tier, and not an add-on module.
Deliberately not building
- Marketing automation — a different product; competitors bundle it and do it badly
- Full accounting and general ledger — we integrate with QuickBooks, we do not try to become it
- Payroll — a regulatory surface far outside what we should touch
- Collision and body estimating — different data, different workflow, different buyer
- Parts counter retail — this is a repair shop system, not a point of sale
Written down so that scope drift has to be an argument rather than an accident.
The repair order
Every line carries its own answer.
Approved, declined, deferred to the next visit, or still waiting on the customer — recorded per line, with who took the approval and when.
Declined work doesn’t disappear. It stays on the vehicle’s record and comes back around, which is revenue already sitting in your customer file.
RO 1044 · 2021 Silverado J. Whitfield · 84,112 mi
| Work | Customer said | Amount |
|---|---|---|
| Front brakes — pads & rotors | Approved | 612.40 |
| Serpentine belt | Approved | 184.00 |
| Four-wheel alignment | Declined | 135.00 |
| Rear shocks | Next visit | 640.00 |
| Coolant flushFound by tech | Waiting on customer | 189.00 |
Adding the coolant flush would put this over the
10% ceiling on the authorized amount. Approved: 796.40 · ceiling: 876.04
Approved by phone · Tue 9:14 AM · taken by Dana R.
Parts · RO 1042 4 suppliers · live
| Supplier | Part | On hand | Your cost |
|---|---|---|---|
| O’Reilly2.1 mi · Congress Ave | Ceramic, front setBP-40871 | 6 in stock | 62.40 |
| NAPA3.4 mi · Ben White | Ceramic, front setNB-7729C | 2 in stock | 68.15 |
| AutoZone1.6 mi · S 1st | Premium, front setDP-1188 | Tomorrow AM | 59.80 |
| WorldPacNext-day | OE equivalentWP-55210 | Next-day | 91.05 |
Your markup matrix sets the sell price automatically.
Parts
Every supplier you buy from, in one search.
Search your existing supplier accounts at once — your negotiated pricing, current availability, and local stock. Add a part to the repair order and the purchase order follows.
We neither see nor set your pricing. What you pay stays between you and your
supplier, and we take no margin on parts. You can reach about 20,000 stores this way, including dealer parts departments and local jobbers.
Invoicing
Your shop’s name on it, not ours.
Your logo, address, license numbers, and wording — all of it editable, the same way you’d change an email signature. If your state requires specific language on a repair order or an invoice, you can put it there yourself.
Texas tax is handled correctly — labor isn’t taxed, parts are, and the tax is broken out by state, city, and transit for filing. An invoice reprinted in December looks exactly like it did the day it was issued, even if the shop’s branding has changed since.
Invoice 1042 Issued Tue 10 Aug
Whitfield Automotive1420 S Congress Ave · Austin, TX
(512) 555-0148
(512) 555-0148
Invoice 1042M. Alvarez
2019 Ford F-150 · 61,204 mi
2019 Ford F-150 · 61,204 mi
| Front brakes — labor2.4 hrs | 348.00 |
| Brake pads — front set | 109.20 |
| Rotors — pair | 154.18 |
| Shop supplies | 17.40 |
Subtotal628.78
Sales tax — parts only, 8.25%21.73
State 16.46 · City 2.64 · Transit 2.63
Total650.51
Getting paid
Card numbers never enter the software.
Card data passes directly from your customer to your processor. It never travels through AutoShop, is never written to your database, and never appears in a log. What your system keeps is a token, the last four digits, and the amount — and none of that reaches us either.
Card at the counter
Chip reader or contactless.
Send a payment link
Texted to the customer — paid from their phone.
Cash or check
Recorded, with a printed receipt.
Split payment
Across cards, or part now and part on account.
You keep your processor and your rates. AutoShop connects to the merchant
account you already have rather than putting itself between you and your money. Change
processors without changing software.
Messages · M. Alvarez Consent on file · 12 Mar 2026
Tue 9:06 AM
Whitfield Automotive: your estimate for the F‑150 is $650.51 —
front brakes, pads & rotors. Reply YES to approve, or call us at (512) 555-0148.
YES
Approved, thank you. We’ll have it completed today.
Tue 3:41 PM
Your F‑150 is ready for pickup. You can pay in advance here:
pay.processor.com/…
Every number carries a timestamped consent record. An inbound STOP
revokes it immediately and permanently.
Customer messaging
Approval by text, with consent on the record.
Estimates approved from the customer’s phone, ready-for-pickup notices, and follow-ups on work they declined — raised again after 90 days.
Consent is a database record with a timestamp and a source, not a checkbox someone remembers checking. Transactional messages and marketing are separate permissions with separate opt-outs, and reminders queue rather than firing at 3 a.m.
Your carrier account, your number. Messages go out through the messaging account you already hold. We don’t sit between you and your carrier, and we take no cut of what you send.
Reporting
The numbers you already manage by.
Effective labor rate, gross profit split the way the trade splits it, average repair order and technician efficiency — calculated the way the industry calculates them, so the figure on screen is comparable to the benchmark you measure against.
Reports · month to date 147 cars
Average RO$584▲ 6.2% · benchmark 400–550
Gross profit54.1%benchmark 50–60%
Labor GP72.4%benchmark 70–80%
Parts GP33.8%▼ under benchmark 35–45%
Effective labor rate$118posted rate $145
Car count147last month 139
| Declined work — still on file | Times | Value |
|---|---|---|
| Alignment | 14 | 1,890 |
| Rear shocks | 6 | 3,840 |
| Coolant flush | 9 | 1,701 |
Revenue already present in your customer records.
Because the database is yours and runs on your hardware, your bookkeeper or accountant can query anything we didn’t build a report for. That capability isn’t ours to withdraw.
At the counter
Hand every customer their service record.
Every invoice you print carries a QR code. The customer scans it and the visit lands in Scissa for Drivers — the vehicle, the odometer, the work, your shop’s name, the date, the total.
It takes four seconds, it costs you nothing, and it needs no signup and no email capture. The record travels inside the printed code, so nothing leaves your box to make it work — and when they sell the car, your shop’s name is in the history that goes with it.
No cloud competitor can match this without asking your customers to open an account with the vendor.
Printed on invoice 1042
Whitfield Automotive
2019 Ford F-150 · 61,204 mi
Illustration only — not a working code.
Ownership
You own the hardware and the data on it.
This is the opposite of how the rest of the industry operates, and it’s the reason the system runs on hardware in your shop rather than in a vendor’s data center.
The hardware is yours
You bought it and it sits in your building. Move it, secure it, or replace it like any other piece of shop equipment.
The database is yours
Every customer, vehicle, repair order, and invoice is held in a standard database on that machine. Give your accountant access, connect your own reporting tools, query anything we didn’t anticipate.
No remote shut-off
There is no kill switch, because none was built and none will be. Stop paying for support and you lose updates and our help — never your invoices, your customers, or your history.
Export at any time
Your entire database, in full detail — not a summary and not a set of PDFs. Available whether or not you hold a current support plan.
Support access is yours to grant
Remote access is disabled by default. You enable it when you want help and it expires on its own. Every session is written to a log you can review.
No dependency on us
Nothing to renew and no server to check in with. If we went out of business tomorrow, the system in your office would open on Monday exactly as it did on Friday.
Security updates are provided free, indefinitely, to every system we have sold
— regardless of support status or software version. A shop holding its customers’
names, addresses, and vehicle records shouldn’t have to keep a subscription current just to stay patched, so that protection isn’t tied to one.
Ask every vendor these three
Three questions worth asking any vendor you’re considering.
01
Can I run my own reports against my own data?
If the answer needs a paid export or an API tier, the data isn’t really yours.
02
Can you disable my system?
Ask whether the capability exists, not whether they would ever use it. Most vendors won’t answer that version.
03
Exactly what do I receive if I leave?
“A CSV of customers” isn’t your history. Ask to see the export before you sign.
Those answers are why this product is built the way it is.
No lock-in
Your suppliers. Your processor. Your accounts.
You already hold supplier relationships and negotiated rates. AutoShop connects to them rather than replacing them, and we take no percentage.
Card processing
Your merchant account and your rates. Card numbers pass directly from the customer to your processor and never enter the software.
Text messaging
Your carrier account and your number.
Parts suppliers
Your accounts and your negotiated pricing, in a single search.
Offsite backup
Our managed service, or your own storage. Encrypted before it leaves the building in either case.
Bookkeeping
Invoices and payments sync to QuickBooks. The books remain yours.
Your devices
Any tablet, phone, or PC with a browser. Nothing proprietary to buy from us.
What it costs
Buy it once. The only recurring cost is optional.
| Five years, one shop | Up front | Per year | Five-year total |
|---|---|---|---|
| Scissa AutoShop — appliance + perpetual license | $7,495 | $0 | $7,495 |
| … with Care+ and managed backup | $7,495 | $1,656 | $14,119 |
| Cloud shop management — $179/mo | $0 | $2,148 | $10,740 |
| Cloud shop management — $2,000/mo | $0 | $24,000 | $120,000 |
The appliance price includes the hardware and the first year of Care+ ($99/mo) and managed offsite backup ($39/mo). From year two both are optional — drop them and you owe us nothing further, and you keep a fully working shop. Security patches are free forever either way, on every box we have ever sold. Cloud comparison is list pricing across the category at $179–$2,000 per month, August 2026.
What’s included
No seats. No tiers. No add-ons.
The cloud model bills by the thing you did more of — another technician, another bay, another location, a report you needed. One price here covers the shop, and it does not move because you grew.
| What you might expect to pay extra for | Scissa AutoShop | Typical cloud plan |
|---|---|---|
| Service writers, technicians, and owners | Unlimited users, included | Billed per seat, every month |
| Fleet and commercial accounts | Included, in the first release | Usually a higher tier |
| Bays, tablets, and front-desk terminals | As many as you like | Often capped or billed per device |
| Reporting and analytics | Every report, included | Commonly gated to a higher tier |
| Getting your data out | Free, full fidelity, any time | Paid export, or an API add-on |
| Querying your own database directly | It’s your database | Not offered at any price |
| Digital inspections with photos | Included with Care+, next release | Frequently a separate paid module |
| Photo and attachment storage | Whatever the disk holds | Quota, then overage |
| QuickBooks sync | Included with Care+, next release | Often an integration fee |
| Parts ordering across suppliers | Included, and we take no margin | Sometimes an add-on, sometimes a rebate we never see |
| Card processing | Your processor, your negotiated rates | Often required, at their spread |
| Customer texting | Your carrier account and number | Per-message, or prepaid credits |
| Onboarding and training | Included in the appliance price | One-time implementation fee |
| A second location | A second box you also own | Another full subscription |
| Security patches | Free forever, every version | Only while you keep paying |
The right-hand column describes how shop management is commonly sold, not any one vendor’s price list. Read your own quote — the number on the front page is rarely the number on the invoice, and the gap is usually seats, locations, and the reports you actually wanted.
Talk to us about AutoShop
See it running in a real shop.
Tell us roughly how many bays you run and what you’re using now. We’ll come back with an honest answer about whether it’s a fit — including when it isn’t.
Your team is already using AI with your documents.
The only question is whose servers those documents are on.
Scissa Redoubt is a private AI assistant that answers questions about your company’s own files — contracts, case files, project records, policies, drawings, reports. It runs on a box in your office, with no connection to the outside world. Nothing you ask it, and nothing it reads, ever leaves your building.
You
What are our notice requirements under the Henderson agreement?
Redoubt
Either party must give sixty days’ written notice to
terminate for convenience, delivered by certified mail to the address in Schedule A.
Termination for cause requires written notice and a thirty-day cure period. Notice by email is not sufficient under § 14.2.
1
Henderson_MSA_executed_2024.pdf§ 14.2 Notice · page 22
2
Henderson_MSA_executed_2024.pdfSchedule A — Addresses for notice · page 41
3
Henderson_Amendment_2_2025.docx§ 3 — amends cure period · page 2
Answered from 3 documents you have permission to open. 2 matching documents were excluded because you don’t.
The problem
Banning it doesn’t work. People will use their phones.
Your staff have already found AI useful. They are pasting client contracts into a chat window to get a summary, uploading case files to get a first draft, dropping engineering specs in to ask a quick question.
Most of them aren’t being careless. They are being productive, with the only tool available to them.
But every one of those documents is now sitting on a server owned by a company you have no relationship with, under terms you didn’t negotiate, in a jurisdiction you didn’t choose. For some organizations that’s uncomfortable. For firms with confidentiality obligations to clients, contractors handling controlled technical data, or practices holding patient records, it’s a problem a policy memo can’t solve.
The answer is to give them something better that never sends the file anywhere.
What Redoubt is
A dedicated appliance that answers questions about your own documents.
Your staff open a browser, ask a question in plain language, and get an answer drawn from your files — with a citation showing exactly which document and which section it came from, so anyone can check the source.
The AI model itself runs on that box. Not in a data center. Not in a vendor’s cloud. On hardware physically in your office, that you own, that you could unplug.
re·doubt (n.) — a small, self-contained fortification, built
to hold its own position without a supply line.
We named it after the thing it is. Everything Redoubt needs is inside the box. It has no supply line, because it doesn’t need one — and because a supply line is the thing an attacker follows home.
We named it after the thing it is. Everything Redoubt needs is inside the box. It has no supply line, because it doesn’t need one — and because a supply line is the thing an attacker follows home.
We size and supply the hardware
Built to fit your organization and delivered configured. It plugs into power and your network.
You point it at your documents
A shared drive, a document management system, a folder structure — it reads what you give it access to and nothing else.
Your staff open a browser
Any computer, tablet, or phone on your network. Nothing to install on every machine, no per-seat licensing.
You control who sees what
Existing permissions carry through. Roles and access are administered by you.
Why this is different
Different in kind, not in degree.
Most “private AI” means a cloud vendor has promised in a contract not to train on your data. That is a promise, and promises are only as good as the company behind them and the terms they can revise.
The documents never leave
Not encrypted in transit — never sent. The model, the index, and your files live on the same machine on your network. No vendor has a copy. No third-party breach can expose them, because no third party has them.
It cannot browse the web
No web search, no outbound calls. The moment a system can reach the outside world, “what did it send, and when?” becomes a question you keep answering. Redoubt answers it once: nothing, ever. It can run fully air-gapped.
It respects who may see what
Where most document-AI projects quietly go wrong: files get indexed into one pile, permissions flatten, and someone gets a paragraph from the partner compensation sheet. Redoubt checks permission at the moment the question is asked.
Every question is recorded
A complete, local, tamper-evident log of who asked what and what came back. When a compliance officer, a client, or an auditor asks how AI is being used with sensitive material, you have an answer rather than a shrug.
It works when the Internet is down
Because it never needed it. An ISP outage doesn’t take your assistant offline, and it doesn’t change a single thing about how it answers.
You own it
The appliance and a perpetual license. Stop paying for support and the box keeps working indefinitely, with all your documents, exactly as it did the day before. There is no remote switch. We do not build one.
What you can ask it
- Answer a question from your files. “What are our notice requirements under the Henderson agreement?” — with a citation to the clause.
- Find things by meaning, not filename. Locate the document you’re thinking of without remembering what someone named it in 2019.
- Summarize. A 90-page report, condensed, in seconds.
- Compare and extract across documents. Pull the same term out of forty contracts.
- Get a new person up to speed without interrupting someone senior.
What it deliberately does not do
We’d rather you know this now than find out after you sign.
- It doesn’t search the web. By design.
- It doesn’t send anything anywhere. No analytics on your content, no telemetry containing your text, no “anonymized” samples.
- It isn’t a general-purpose assistant. It won’t write you a poem or explain quantum mechanics well. It’s very good at one job.
- It doesn’t make an answer true by itself. Every answer carries its sources so a human can verify. AI systems make mistakes. Ours shows its work, so you can catch them.
Who this is for
Organizations where the location of a document is an obligation, not a preference.
Law firms
Client confidentiality, and outside counsel guidelines that increasingly prohibit third-party AI tools touching client material.
Accounting and tax practices
Client financial records held under professional duty.
Defense and aerospace suppliers
Controlled technical data with handling requirements that cloud services complicate.
Healthcare practices
Patient records, and business associate obligations you would rather not extend to another vendor.
Engineering, architecture, manufacturing
Designs, drawings, and process knowledge that are the actual value of the company.
Anyone who has been asked in writing
Whether client material is being put into an AI system. If the honest answer is “probably, and I am not sure which one,” this is for you.
Hardware
The hardware is our problem, not yours.
You’re not buying a parts list, and you don’t need someone on staff who knows how to spec one.
What you buy is a working system that answers questions about your documents. How that gets built is a detail we handle.
We size it to your organization
How many people will use it, how many documents it holds, how quickly answers need to come back. A 12-person practice and a 200-person firm don’t get the same box, and neither should pay for the other’s.
We build, configure, and deliver it
It arrives assembled, installed, and tested. No procurement exercise, no compatibility list, nothing for your IT provider to research.
We keep it running
Support covers hardware as well as software. A failed component is our obligation, not a ticket you open with a manufacturer.
It grows when you do
Capacity is added as you outgrow the original sizing — and organizations that need it can run separate units to keep practice groups, programs, or client matters fully isolated.
Get started
Every Redoubt is sized to the firm it serves.
There is no configurator and no self-serve checkout, because the right box depends on how many people use it, how many documents it holds, and how fast answers need to come back.
Tell us those three things and where your documents live today, and we’ll come back with a scope and a number. First deployments are quick — most of the work is pointing it at your files and getting permissions mapped correctly.
Your lot runs on three subscriptions. It should run on one box.
Scissa AutoSales is dealership management for a small independent used-car lot — inventory and photos, cost basis and gross, deal desking, Texas title and plate work, and your listings pushed out to the classified sites. One machine on your network, bought once, and the data on it is yours.
What it replaces
Three vendors, one bill, and none of them talk to each other.
A lot doing this properly today pays a DMS, a website vendor, and listing subscriptions separately. That is roughly $190 to $500 a month — $11,000 to $30,000 over five years — and the inventory has to be keyed in more than once.
Inventory and photos
VIN decode, condition notes, 30–50 photos a unit with ordering and a primary shot. Shoot from a phone on the lot — including out at the back fence where the WiFi does not reach.
Cost basis and gross
Acquisition, transport and every reconditioning line item against asking price, so the gross on a unit is a number you can see rather than one you work out later.
Deals, titles and plates
Deal desking, and the Texas title and plate work that follows it. A dealer cannot half-title a car, so none of this ships in pieces.
Listings and your website
Published from the box. Not served by it.
Your inventory pages and photo variants are built on the box and pushed out to hosting. Nothing on your network listens to the open internet, which is the whole reason a machine holding customer records can sit safely on a dealership LAN.
Syndication that is a file, not an integration
Autotrader, Cars.com and CarGurus all take dealer inventory as a feed. The box builds each one to that destination’s field mapping and photo specs and sends it. No middleman holds your inventory.
Leads come back to you, not to us
A shopper filling in a form on your site reaches your email and your phone number. The box collects from those. We never hold a queue of your prospects — their names and numbers are your business, not ours.
What it deliberately does not do
We do not take credit applications.
Financing goes out through your lender’s own portal, and the box keeps only the outcome — lender, approved terms, contract number, status.
A credit application means a social security number, a date of birth, income, an employer and a driver’s licence photograph sitting on a computer in a sales office. Holding that would put your dealership at the centre of the FTC Safeguards Rule on day one.
The safest way to never leak an SSN is to never hold one. It is the same rule we apply to card numbers, pointed at a different kind of poisonous input.
In development
Being built now, in the open.
AutoSales is not shipping yet. It is aimed at a Texas lot carrying 20 to 100 units, with a GDN, currently paying two or three vendors. If that is you, the useful time to talk to us is while the decisions are still being made.
Your car’s service history. On your phone, not on our servers.
A free app that keeps a complete maintenance record for your vehicle — every repair, every date, every odometer reading. There is no account to create, no server holding your history, and no company that can lose it, sell it, or shut it off.
Free forever for one vehicle
No account, no sign-up
No ads, no subscription
Backs up to your iCloud or Google account
2019 Ford F-150 61,204 mi
| Front brakes — pads & rotorsWhitfield Automotive · 10 Aug 2026 | 650.51 |
| Oil & filter, tire rotationWhitfield Automotive · 2 Mar 2026 | 89.40 |
| State inspectionQ Lube · 18 Nov 2025 | 45.50 |
| Serpentine beltWhitfield Automotive · 4 Jun 2025 | 184.00 |
Next up — oil change
due at 66,000 mi, about 4,800 miles out.
At the counter
Scan the code on your invoice. That’s the whole process.
Every invoice printed by a shop running Scissa AutoShop carries a QR code. Point your camera at it and the visit lands in your history — the vehicle, the odometer, the work performed, the shop, the date, and the total. Nothing to type and nothing to check.
The record travels inside the code, not through us. Your service history
is carried in the part of the link that browsers never transmit, so it goes from the paper
in your hand straight into your phone. It never reaches a Scissa server, and it never
appears in a log — because there is no server in the path at all.
Haven’t installed the app yet? The same code opens a plain page showing your record, put together entirely on your own phone. Install later and scan again.
Printed on your invoice
Invoice 1042 · Whitfield Automotive
2019 Ford F-150 · 61,204 mi
Illustration only — not a working code.
Any shop, not just ours
Three ways in. You will use whichever one you have.
Most people’s cars have been serviced by shops that have never heard of us. The app is built for that, so your history can start with the folder in your glovebox rather than with your next visit.
Scan an AutoShop QR
Exact, structured, instant. Nothing to review and nothing to correct, because the shop’s system wrote the record rather than a camera reading it.
Share an emailed invoice
Send the PDF to the app from your mail app. Most shop invoices are real text, so the details come across cleanly.
Photograph the paper one
Your phone reads it and fills in the form. You confirm before anything is saved — this saves the typing, it does not guess on your behalf.
Reading happens on your phone, using the text recognition already built into it. No photo of your invoice, and nothing read from it, is ever sent anywhere — not to us, and not to some other company’s service for parsing.
What it costs
Free for one vehicle, forever. $2.99 once for the rest.
Free
One vehicle, full history
- Unlimited service records for one vehicle, kept forever
- All three ways of getting records in
- Backed up with your phone, to your own iCloud or Google account
- No advertising, ever
- No account and no sign-up
Scan at the counter and you have your record. There is no payment step in the way, and there never will be.
$2.99 · one time
Everything else
- As many vehicles as you own
- Service reminders by mileage and by date
- Export to PDF or CSV whenever you want
- A resale history report for when you sell the car
One purchase. Not a subscription, and not a trial that expires.
No ads was a decision, not an oversight. Auto services is a heavy local
advertising category, which means an ad-supported version of this app would end up showing your
shop’s competitors to the customer your shop just handed it to. We would rather charge
$2.99 once.
Your data
We could not look at your history if we wanted to.
No account
Nothing to sign up for, no email address, no password. There is no user record because there are no users to record.
No server of ours
Your history lives on your phone, and in your own device backup if you use one. We operate no database that holds it, so there is nothing of yours for anyone to breach, subpoena, or buy from us.
No tracking SDKs
The app ships with no third-party code in it at all, which is what lets its store privacy label read No Data Collected.
Backed up the way the rest of your phone is
Your history is included in your normal device backup — iCloud on an iPhone, your Google account on Android. Replace a lost phone or move to a new one and your service records come back with your photos and your messages, without anyone having to do anything special.
That backup is yours, in your account, under your Apple or Google credentials. It does not pass through Scissa, and we have no more access to it there than we do on the phone itself.
The trade-off, stated plainly
There is no Scissa cloud to fall back on, by design. If you have turned your device backup off, the only copy is the phone in your pocket — lose it and the history is gone.
Export to PDF or CSV is in the paid tier, and the app will nudge you to use it before a long gap. We would rather tell you this here than have you find out later.
For shops
Something to hand a customer that your competitors cannot.
If you run Scissa AutoShop, the QR is already on your invoices. “Scan this and your service record is in your pocket” takes four seconds at the counter and costs you nothing.
Your customer leaves with a permanent, portable record of the work you did, with your shop’s name on every line of it. When they sell the car, your name is in the history. A cloud competitor cannot match this without asking your customers to open an account with the vendor.
What the shop has to do
- Nothing. The code prints on the invoice by default.
- No customer signup, no email capture, no list to manage.
- No data leaves your box — the record is in the printed code, not in a transfer.
- Works whether or not the customer ever installs anything.
You have the idea. We build it.
Most projects arrive as a description of a problem, not a specification. Our job is to turn that into software that runs in front of real users — and to hand you everything needed to keep it running without us.
The method
Four steps, and you can stop after any of them.
Each phase ends with something you own and could hand to another firm. That’s deliberate: it’s the only honest way to sell the next phase.
Decide whether to build
Two to three weeks. We map the problem, talk to the people who will use it, and produce a written scope with a fixed number attached. Sometimes the finding is don’t build this, and we’ll say so.
Something you can click
The riskiest part of the system, working, early. Not a mockup — running software with real data, so the argument is about behavior instead of screenshots.
Ship in slices
Two-week slices, each one deployable. You see progress in the running system rather than in a status report, and priorities can change without renegotiating the whole engagement.
Leave properly
Documentation, a runbook, the infrastructure in your accounts, and a walkthrough with whoever inherits it. Booked at the start of the project, not squeezed in at the end.
What we take on
- Line-of-business systems that replace a spreadsheet holding a company together
- Software that has to keep working when the Internet does not
- Anything involving money, invoicing, or an audit trail that has to reconcile
- On-premises and self-hosted deployments other firms would rather not touch
- Rescue work on a system someone else left half-finished
What we turn down
- Staff augmentation — a body in your standup isn’t what we’re good at
- Fixed-price builds from a spec we had no part in writing
- Work where nobody on your side can make a decision within a week
- Projects whose success depends on a platform we cannot test against
- Anything requiring us to hold card numbers or sell customer data
Your data during the engagement
We’d rather not hold your production data at all.
The same instinct behind the products applies to the work we do for you. Every copy of your data that exists is a copy that can leak, and the cheapest way to protect it is not to make one.
Synthetic data by default
We build and test against generated or anonymized data unless the work genuinely can’t be done that way — and then we say so in writing first.
Your accounts from day one
The repository, the cloud accounts, the domains, and the secrets are yours from the first commit. We work inside your perimeter rather than building a copy of it inside ours.
Access that expires
Named accounts, scoped to what the work needs, on a schedule that ends at handover. Revoking us should take one afternoon and no negotiation.
We sign your NDA
Not ours. If your legal team has its own NDA, we start there instead of sending you a form to sign.
No portfolio without permission
We won’t name you, screenshot your product, or write it up without your explicit sign-off — including after the engagement ends.
We delete what we held
At handover, and we tell you what there was and confirm when it’s gone. Written into the statement of work, not left to good intentions.
Ownership
You own the source, the infrastructure, and the right to fire us.
Assigned to you on final payment, in writing, in the contract you sign at the start. No license-back, no runtime fee, no component only we can maintain. The same promise as the products, applied to work we do for you.
Start a project
Tell us what is broken.
You don’t need a spec. A paragraph about what is painful today is a better starting point than a document describing a solution.
We reply to every inquiry within one business day, including the ones we turn down — with the reason.
Small on purpose. Written down on purpose.
Scissa builds software for businesses that got tired of renting it. We’re deliberately small, we work on a few things at a time, and we write down every decision we make so that the reasoning outlives whoever made it.
Designed in Texas. Runs anywhere in the world.
Because the software runs on a machine in your building rather than in a data center we picked, there is no region to choose, no residency question to answer, and no border your business data has to cross. A shop in Amarillo and a firm in Auckland run the same box on the same terms.
100% independently owned
No investors to answer to
Why we exist
Because software rent has no ceiling.
A shop owner told us their management software had gone up four times in six years and they couldn’t leave, because leaving meant losing a decade of history. That’s not a pricing problem. It’s an architecture designed to punish a customer who wants to leave.
Everything here is a reaction to that. If the software runs on your hardware and the data is in a format you can export, the vendor has to earn the renewal every year. We think that’s the right amount of pressure to be under.
You own your data, and you can leave whenever you want. Your records sit on
your hardware in a standard database, and you can take all of it — in full detail, not a
summary — on any day you choose, whether or not you are currently paying us. No notice
period, no export fee, no call with someone whose job is to talk you out of it. If we stop
being worth the money, take everything and go. That is not a policy we could quietly revise;
it is how the software is built.
We write the decision down
Every significant technical choice gets a record: what we picked, what we rejected, and what it costs us. The bad consequences are a required section.
We never hold card numbers
Card data goes from the customer to the processor and never through the software we build. Not encrypted, not briefly — never.
We assume the Internet is down
Every product is designed around the outage first and the happy path second, because that’s the order in which they matter.
We build no kill switch
Not “configured not to.” There’s no code path that can stop a customer from working because a license lapsed.
Working with us
If we’re the wrong choice, we’ll tell you on the first call.
We’d rather lose the work than take a project we can’t do well. It’s a smaller business and a much better one.
We hire rarely, and slowly.
A small team means every hire changes the company. We’d rather leave a role open for six months than fill it in three weeks with the wrong person.
Open roles
Three open, all remote.
The salary band, the actual day-to-day, and what the job is not are all below — before you apply, not after the third interview.
Open
Senior Front-End Engineer
Own the front end of software people use all day to run their business — on a counter, a workshop tablet, and a phone.
$130,000 – $185,000
Remote (United States) · Full-time
Read the full role → OpenSenior Back-End Engineer
Own the back end and the data model for software that handles money and runs unattended for years.
$140,000 – $195,000
Remote (United States) · Full-time
Read the full role → OpenAI Engineer
Own retrieval and local inference for a system that answers questions about an organization’s own documents, with no cloud API in the path.
$115,000 – $160,000
Remote (United States) · Full-time
Read the full role →None of these is you, but you want to work here? Introduce yourself anyway.
How we hire
01
02
03
04
No trick questions, no unpaid projects.
A real conversation
45 minutes about what you’ve built and what you want to build next. We’ll tell you the salary band on that call.
Look at real code
We read something you’ve written, or we pair on something of ours. No algorithm puzzles, no whiteboard.
A paid day
If we’re both still interested, a day of actual work at your normal rate. Best signal either side can get.
An answer, fast
Yes or no within two business days of the last conversation, with a reason. No silence.
What it’s like here
Small enough that you’ll touch every part of a product. You’ll write documentation, and it’ll be reviewed as carefully as the code. You’ll talk to customers directly.
What it’s not
Not a big-team environment with a clear ladder. Not a place with a large budget. If you want deep specialization in one layer, we’re the wrong place, and we’ll say so early.
Senior Front-End Engineer
Own the front end of software people use all day to run their business — on a service counter, a tablet in a workshop, and a phone between jobs.
You must be authorized to work in the United States. We do not sponsor or transfer work visas.
About the work
We build software that runs on hardware our customers own rather than in someone else’s cloud. The interfaces we write have to be fast, work without an Internet connection, and hold up in places software usually isn’t.
You would own the front end. Not a slice of it, and not inside an architecture someone else already decided.
What we use
TypeScriptReactModern build toolingCSSHTML
TypeScript in strict mode, types shared end to end. No any.
What you’d do
- Own the front-end architecture — state, component boundaries, testing strategy — and live with those decisions for years
- Build for desktop, tablet, and phone, where each is a different job rather than a different screen width
- Make the application work with no network connection, and make that state legible without alarming the person using it
- Set the accessibility bar and hold it: contrast measured rather than guessed, status never carried by color alone
- Maintain a shared component library used across more than one product
- Write the documentation that outlives you on it
What we’re looking for
- 8+ years building production web applications, at least 4 of them in React
- You have owned a front end end to end — architecture, conventions, and testing strategy were yours, and you were still there when the consequences arrived
- You have made a call you later regretted, at scale, and can describe what you’d do differently. Seniority here is measured in decisions and their aftermath, not years
- Deep CSS fluency — layout, cascade, and why a thing renders the way it does
- Experience where accessibility was a requirement rather than an audit finding
- You review other people’s code well, and can explain a decision to someone who isn’t an engineer
Nice to have
Offline-first or local-first applications · design systems you maintained rather than consumed · field, industrial, or point-of-sale software · native iOS or Android.
What this job is not
There is no architect above you and no team to hide in — if the front end is wrong, it is wrong because of a decision you made. Not a big team with a clear ladder, and not a place with a large budget. You’ll write documentation that gets reviewed as carefully as your code, you’ll talk to customers directly, and you’ll work outside your title. If you want deep specialization in one layer, we’re the wrong place and we’ll say so early.
How to apply
No cover letter. Send us something real.
Send us something you’ve built — code we can read beats a résumé. Tell us about a UI decision you got wrong and what it taught you.
We read everything that comes in, but we cannot reply to every application — there are not enough of us, and we would rather say that than let you wonder. Once we have spoken, you get an answer within two business days of that conversation, including a no, with the reason.
Senior Back-End Engineer
Own the back end and the data model for software that handles money, runs on machines our customers own, and has to keep working unattended for years.
You must be authorized to work in the United States. We do not sponsor or transfer work visas.
About the work
Our software runs on machines our customers own, often with no one nearby and sometimes with no Internet. It handles money, customer records, and payments. The hard problems here are correctness and failure handling, not scale.
You would own the back end and the data model, and you would be the person accountable when either is wrong.
What we use
TypeScriptNode.jsPostgreSQLSQLDockerLinuxAWS
TypeScript in strict mode, types shared end to end. No any.
What you’d do
- Own the database — schema design, queries, indexes, and migrations that execute unattended on a customer’s machine with nobody watching
- Design APIs with types shared end to end, and validate everything crossing a boundary
- Get money exactly right. Integer arithmetic, never floating point, totals that reconcile to the cent, and tests written specifically to break them
- Handle failure deliberately — retries, idempotency, dead letters. We don’t swallow errors, and a failure that quietly becomes null is one nobody will ever find
- Build the audit trail: who changed what, when, and what it looked like before
- Own security in what you write — password hashing, sessions, and authorization checked on the server for every request
What we’re looking for
- 8+ years of production back-end work, at least 4 in a typed language
- You have owned a production database — you designed the schema, wrote the migrations, tuned the queries when they got slow, and have personally performed a restore
- You have been on the hook when something broke in production at 2 a.m., and you changed something afterward so it couldn’t happen the same way twice
- Real SQL. You can read a query plan and explain why a transaction boundary is where it is
- Experience with money, billing, tax, or anything else where being off by a cent is a defect rather than a rounding artifact
- You design systems rather than endpoints, and can say plainly why you rejected the alternative
Nice to have
Payments or PCI-adjacent work · self-hosted or on-premises products · Linux administration · AWS beyond the console · security review or threat modeling you led.
What this job is not
There is no principal engineer above you to escalate to. Not a microservices estate, and not high-scale distributed systems — the interesting constraint is a single machine that must never lose data or need a site visit. Not a place where “we’ll add tests later” survives review.
How to apply
No cover letter. Send us something real.
Tell us about a bug that cost real money and what you changed so it couldn’t happen again.
We read everything that comes in, but we cannot reply to every application — there are not enough of us, and we would rather say that than let you wonder. Once we have spoken, you get an answer within two business days of that conversation, including a no, with the reason.
AI Engineer
Own the retrieval and inference behind a system that answers questions about an organization’s own documents — running entirely on a machine inside their building, with no cloud API in the path.
You must be authorized to work in the United States. We do not sponsor or transfer work visas.
About the work
We have built a system that answers questions about an organization’s own documents — contracts, case files, project records, policies — and it runs entirely on a machine inside that organization’s building. No cloud API, no hosted model, no outbound call of any kind. It can operate fully air-gapped.
That constraint is the whole job. Every problem you would normally solve by sending it to a bigger model somewhere else has to be solved on hardware we ship, and every answer has to cite the document and section it came from so a human can check it.
What we use
PythonTypeScript
PostgreSQLLinux
DockerGPU inference
Open-weight language models, embeddings, and vector search — running locally.
What you’d do
- Own the ingestion pipeline — parse real-world documents, chunk them sensibly, embed them, and keep the index current
- Make retrieval return the right passage, and the citation that goes with it: page, section, source
- Keep permissions part of retrieval rather than a filter applied afterward. If a person can’t open the document, they can’t get an answer from it — and that has to hold at query time
- Choose, quantize, and evaluate open-weight models against questions real users actually ask, on hardware we can afford to ship
- Build the evaluation harness, so “it got better” is a measurement rather than an impression
- Make it fast enough that someone at a desk doesn’t go make coffee while it thinks
What we’re looking for
- 3+ years writing production software in Python, TypeScript, or both
- Hands-on experience with language models beyond calling an API — retrieval, embeddings, vector search, chunking strategies, and why each of them fails
- You have measured whether a change improved things, and can describe how. Vibes are not an evaluation
- Comfortable on Linux and in containers, and not frightened by a GPU utilization graph
- You will say “I don’t know, let me test it” out loud, in front of people
You do not need a graduate degree, published research, or experience at frontier scale. You need to have built something in this space that worked, and to know why it worked.
Nice to have
Local or open-weight model serving and quantization · document parsing at scale, including messy PDFs and OCR · an information retrieval background predating the current wave · access control or permissions modeling · fine-tuning or adapters · on-device inference.
What this job is not
- Not a research role. No papers, no novel architectures. The interesting problems here are engineering ones under a hard constraint
- Not prompt engineering. Prompts are a small part of a system whose harder half is retrieval, permissions, evaluation, and speed
- Not “call the big model.” Sending something difficult to a hosted API is not an available answer — not because of cost, but because the documents are not permitted to leave the building. If that sounds tedious rather than interesting, this will be a frustrating job
- Not a solo role. You would work directly with the engineers who own the database, the API, and the interface around your work. This is a job where you can still ask someone
How to apply
Show us what you measured.
Send something you have built with these tools and tell us how you knew it was working — what you measured, and what you tried that didn’t pan out.
We read everything that comes in, but we cannot reply to every application — there are not enough of us, and we would rather say that than let you wonder. Once we have spoken, you get an answer within two business days of that conversation, including a no, with the reason.
Talk to a person who builds it.
There is no sales team here. The person who answers you is the same person who builds it.
Phone
The fastest way to reach us. If nobody picks up, leave a message and you will get a call back the same business day.
hello@scissasoftware.com
Best for anything that isn’t urgent. Answered within one business day.
Existing customers
support@scissasoftware.com
If your box is down, call (361) 556-6690 rather than emailing — that reaches a phone, not an inbox.
Where we are
5900 Balcones Drive, Ste 100
Austin, TX 78731
United States
We work with customers across North America, and we’ll get on a plane when a project warrants it.
Your data is yours. We designed ourselves out of it.
Most software companies in our categories ask you to trust a privacy policy. A policy is a promise, and promises can be revised by whoever owns the company next. We built the systems so the promise isn’t needed — there’s no copy of your data for anyone to misuse, subpoena, breach, or sell.
We don’t sell data, because we don’t have access to any. Not as a policy
position — as a property of where the software runs. Your business data lives on a
machine in your building, on a disk you own.
Precisely
What we can see, and what we cannot.
This is the specific list. If something isn’t in the right-hand column, we don’t receive it.
Never leaves your building
We have no copy
- Customers, contacts, addresses, vehicles
- Repair orders, estimates, invoices, payments
- Documents and everything inside them
- Message history with your customers
- Your pricing, margins, and supplier costs
- Your reports, and the queries behind them
The complete list of what reaches us
And nothing more
- License identifier and entitlement status
- Software version, and whether the box is healthy
- An encrypted backup, if you opt in — you hold the keys and we cannot read it
- A support session you turned on, which expires on its own and is logged. We have no access without your permission
- Whatever you deliberately send us in an email or a form
The box initiates every one of those connections and accepts none inbound. It sits on your network with no public address, so there’s no door for us — or anyone else — to knock on.
Ownership
Six commitments, each built rather than promised.
The hardware is yours
You bought it and it’s in your building. Move it, secure it, or replace it like any other piece of equipment.
The database is yours
A standard database on that machine. Give your accountant access, connect your own tools, query anything we didn’t anticipate.
No remote shut-off
No kill switch exists, because none was built and none will be. Ask us to prove it and we’ll walk you through where it would have to live.
Export at any time
Your entire database in full detail — not a summary, not a folder of PDFs — whether or not you hold a current support plan.
Support access is yours to grant
Remote access is off by default. You turn it on when you want help, it expires on its own, and every session is written to a log you can read.
Security patches, free forever
To every system we have sold, regardless of support status or version. Staying patched should never depend on whether your subscription is current.
The two hard lines
Where we refuse to be flexible.
Card numbers never touch the software
Card entry happens only through your processor’s own hosted fields or a validated terminal. Your box receives a token in return, and what it stores is the token, the last four digits, the brand, the expiry, the processor’s reference, the amount, and the status. That is the complete list, and none of it is ever sent to us.
This keeps every deployment in PCI DSS SAQ A / A-EP territory. Accepting a card number even once would push every business running the software into full SAQ D obligations — which is why the answer is never rather than rarely.
Nobody gets texted without a consent record
Consent is a row in the database with a timestamp and a source, not a checkbox someone remembers checking. The check happens in the sending layer, so no part of the software can route around it.
An inbound STOP revokes consent immediately and permanently until the customer opts back in. Transactional and marketing messages are separate permissions with separate opt-outs, and reminders queue rather than firing at 3 a.m..
How the software is built
The engineering behind the claims.
Authentication
Passwords hashed with argon2id. Session tokens are 256-bit random values, stored hashed, in httpOnly cookies — never in local storage.
Authorization
Checked on the server for every single request. Hiding a button in the interface isn’t access control, and we don’t treat it that way.
Audit trail
Every change to a financial or customer record writes an entry: who, what, when, before, after. Posted invoices are append-only — corrected by adjustment, never edited away.
Physical security
Disk encryption is assumed. A box in a garage or a records room is physically stealable, and we design for the day someone walks off with it.
No inbound connections
The box accepts none. It initiates every conversation it has with us, which means there’s no webhook, no open port, and no permanent tunnel from our network into yours.
Backups you hold the key to
Encrypted before they leave the building. If you use our offsite service, we store bytes we can’t decrypt. You can also just use your own storage.
Responsible disclosure
Found something? Tell us.
Email security@scissasoftware.com with enough detail to reproduce it. You will get:
- An acknowledgment from a human within two business days
- An assessment and a fix timeline within ten business days
- Credit in the release notes, if you want it
We will not take legal action against anyone who reports a vulnerability in good faith, stays within the scope below, and gives us reasonable time to fix it before publishing.
In scope
- This website and any subdomain of scissasoftware.com
- Our products, on a box you own or one we provide for testing
- The control plane that handles licensing, updates, and backup
Out of scope
- Denial of service, volumetric testing, or anything that degrades a customer’s system
- Social engineering of our staff or our customers
- Findings from an automated scanner with no demonstrated impact
- Any testing against a customer’s live installation without their written permission
A machine-readable version of this policy is published at /.well-known/security.txt. For how this website itself handles visitors, see the privacy policy.
The short version: we collect almost nothing.
It would be strange to sell data sovereignty and then run a website that harvests visitors. This page is short because there isn’t much to describe.
This website
- No third-party analytics. No Google Analytics, no advertising pixels, no social trackers, no session recording.
- No cookies beyond what is needed to make a page work. Nothing to consent to, which is why there’s no consent banner.
- No fonts, scripts, or images loaded from anyone else’s server. Everything on this page came from us, so no third party learns your IP address just because you read it.
- We keep aggregate page-view counts with no personal data attached, on infrastructure we control.
When you fill in a form
We receive what you typed and your email address. We use it to reply to you. Specifically, we do not:
- Add you to a mailing list
- Sell, rent, or share it with a data broker or advertiser
- Use it to retarget you with advertising anywhere
Inquiries are deleted after 24 months unless you become a customer. Ask us to delete yours sooner and we will — and we’ll confirm when it’s done.
Your data inside our products
We don’t have it. Our products run on hardware you own, and the business data lives on that hardware. Our control plane handles licensing, update delivery, health checks, and — if you opt in — encrypted offsite backup that we can’t read.
We can’t query your customers, your invoices, or your history, because there’s nowhere for us to query it from. That’s an architectural property, not a policy we could quietly change.
Your rights
Ask us what we hold about you, ask for a copy, or ask us to delete it, at privacy@scissasoftware.com. We’ll answer within 30 days and we won’t ask why. If you’re in a jurisdiction with statutory data rights, this applies to you regardless of where we are.
Last updated 10 August 2026. If we change this policy materially, we’ll note the change and its date here rather than silently replacing the page.
Terms of service.
Plain-language summary first, because nobody reads the other kind.
Draft. This page is a plain-language outline of the terms
we intend to offer. It has not been through legal review and is not yet a contract. The binding
document is the license agreement and statement of work you sign.
Software licenses
- A product license is perpetual. You buy the right to run that version forever, on the hardware it was sold for.
- Support and updates are a separate annual plan. Letting it lapse stops new versions and support. It doesn’t stop the software.
- There is no remote disable. We have not built one and will not.
- You may export your data at any time, in a documented format, whether or not any plan is current.
Custom development
- You own the work product — source, IP, and deployment — assigned on final payment.
- We keep the right to reuse general knowledge and any pre-existing components, which are licensed to you perpetually and royalty-free.
- Either side can end an engagement at the end of a two-week slice. You pay for what is finished and you keep it.
What we do not warrant
Software has defects. We warrant that we will fix ours under an active support plan within stated response times. We do not warrant uninterrupted operation, and we are not liable for business losses arising from a failure of hardware, network, or a third-party service we do not control.
This website
Content here is provided as-is and may change. Pricing shown on this site is indicative; the number in your quote is the one that counts.
Last updated 10 August 2026.