FAQ

Is this a pilot?

Yes — for both sides. The plant and teaching pages are open. Stripe live card charges are on for this door: authorize at Go, capture only if a usable ZIP ships, void on fail. A code does not skip the card.

Limits are intentional: at most 15 files or 150 MB per job, one job at a time. Over that, we refuse before processing — no charge. You only pay if we deliver a usable package.

Bigger programs: split into separate jobs, ask about a quoted batch, or talk to the operator. After you download the ZIPs, combining them stays in your tools — this public mill does not host that.

What file types do you accept?

Public mill drop (this site): .pdf, .docx, .pptx, .html / .htm, .md, .txt, and spreadsheets (.xlsx, .xls, .csv, .tsv).

Unsupported types are refused before the plant runs — no charge.

Plant magazine (typed stock we also mill): curated email as .eml (Thunderbird Save As from Gmail/AOL/IMAP — not Outlook .pst dumps), contract / agreement text, and filled / lined forms. Those paths are residual-honest prep in the plant; the public bin above is the pay-on-success drop list until we wire more types into this door. When in doubt, convert to PDF or Markdown first, or ask.

What are the size limits?

Per job: 15 files or 150 MB total (whichever comes first). Over that → refuse, no run, no charge. The workspace shows your live count and size before you pay.

What does a brick cost?

$10, for any pile this door accepts, and only if the ZIP ships. A failed or refused job is not charged. A text pile often finishes in minutes. A scan-heavy pile can take about an hour. That is time, not a different price.

Why $10.

How long does a job take?

Small usually finishes while you wait. Medium is often a short wait. Hard often takes about an hour. Start the job, leave if you need to, come back with your pickup code. Download within 72 hours of Ready, then we delete our copies.

How should I prepare my files?

• One subject per job when you can. Manuals in one job, parameter tables in another — not a decade of SharePoint in one drop. See packages, not one giant pile.
• Prefer PDFs that already have text when you have a choice. Pure image scans still work, but they trend Hard. See scanned manuals.
• Mail: export curated .eml from Thunderbird (or convert to PDF/MD). Do not drop a raw .pst — we refuse full mailbox dumps.
• Skip the junk. Website chrome, empty backups, and “final_v2” piles hurt answers. Send what you actually want quoted.
• Optional job label (client + subject) makes the receipt and ZIP easier to file.

When do I pay?

Pay only if we deliver a usable ZIP. Refused or failed jobs are not charged. Stripe places a hold first; we capture only if the package ships, and void if the plant fails. A code does not skip the card.

Full commercial terms (usable package definition, refunds / disputes, liability): /terms.

How do I use the ZIP with my own AI?

KBMill is not a chatbot. You download a portable package and point your model at it.

Simplest path: unzip → open the main Markdown and craft brief → attach or paste them into ChatGPT, Claude, Grok, Gemini, Open-WebUI, LM Studio, or whatever you already use → ask questions from that package only.

For search / RAG in your own stack (chunks, embeddings, mute list), see How to use with your LLM · Portability · Getting started.

How are my files handled?

You keep the ZIP. We do not host your knowledge base. After Ready, you have 72 hours to download if you have not yet. After your first successful ZIP download, we shorten that to about 30 minutes (re-download in that window still works; each download refreshes the grace). Failed jobs clear within 24 hours. Expect this: downloading does not keep our copy for the full 72 hours — save the ZIP locally; the plant copy is meant to go away soon after. Purge removes the job directory, brick, and export ZIP under our work root — see what purge does and does not claim. We do not train on your data.

Built for real technical and business jobs under this plant model — privacy fit. Human access: /privacy §5.2. Diligence: /security.

Uploads arrive over HTTPS into an isolated per-job directory. Other visitors do not see your job. When you start, you get a pickup code — save it and use Package (station 04) if you leave and come back. Do not post pickup codes publicly.

Keep off this hopper: tax docs, medical records, SSNs, passwords, and anything policy forbids on a remote plant (regulated / air-gap / contractual lockbox). Those need a machine you control (open brick library) or an isolated path — ask the operator. Manuals, procedures, and engineering corpora that matter to RAG are what this door is for when policy allows HTTPS processing. Who this door is for.

What do you refuse?

We process legitimate technical, business, research, and historical documents — including piles that matter to production RAG. Illegal or abusive material is refused. Unsupported types and over-limit piles refuse before the plant runs. We do not certify flight, legal, or shop-floor use — your trusted people keep the last word.