Check it on your own history. Keep your data.

This page is for planning, security and procurement teams. It says what Udgass does with data, what safeguards exist, and what does not exist yet. Udgass is early software from one developer. It has no customers, no certifications and has not yet been run on a company’s real data.

Download the assessment kit Jump to what is missing

At a glance

What exists today

What it is	A local, read-only engine (command line, Python standard library only) that replays your past sales, compares its estimates with what happened, flags unusual weeks, compares stock options under assumptions you state, and keeps a tamper-evident record of decisions and runs.
Where it runs	On a computer you control. There is no hosted service and no account.
What it needs	One CSV with date, product and quantity. Nothing else.
What it does to systems	Nothing. It reads the file you point it at. It has no connection to any ERP, planning or purchasing system and cannot place an order.
Who decides	A person. Outputs are advice with stated ranges. A named person makes and owns each decision.
Tested on	Invented data only (97 automated tests, Python 3.9 and 3.13; runs on Windows 11, macOS and Linux). No measurement on real company data exists yet. That is what a pilot is for.

Evaluate it

The demand assessment, on your machine

You need Python 3.9 or newer and a sales export. Leave out customer names, emails and other personal data; columns that look personal are ignored and never stored.

Sales (required)	Date, product code, quantity. Location if you have several. Daily or weekly rows; at least 56 weeks (just over a year), ideally two years or more for a reliable verdict. Monthly totals are not enough. Sample file (synthetic).
Stock snapshots (optional)	Date, product code, quantity on hand. Shows where stock-outs hid demand.
Purchase orders (optional)	PO number, product code, order date, quantity, promised date, receipt date, vendor. Shows real lead times and whether they are changing.
Your past forecasts (optional)	Product code, the first date of each forecast window, and the forecast total for that window, as it was made at the time. Enables a head-to-head comparison.
Formats	CSV in UTF-8, comma, semicolon, tab or pipe separated. Common date formats and decimal commas are handled; ambiguous ones stop and ask. Spreadsheet files must be saved as CSV.

Check the fileShows the columns found, products, weeks, gaps and anything that looks personal. Changes nothing.
```
python3 -m udgass check sales.csv
```
Run the assessmentReplays your history, compares with simple methods and your own forecasts, and writes one report. A temporary working database is deleted when it finishes.
```
python3 -m udgass assess --sales sales.csv --out assessment.html
```
On Windows, type py instead of python3. Typed commands work even where Windows blocks double-clicked scripts.
Share only if you want toAn anonymised copy replaces product and location codes. The report ends with a draft summary in relative figures only, which is never published without your written approval.
```
python3 -m udgass assess --sales sales.csv --anonymise --out shareable.html
```

If Udgass is not clearly better than your current forecast or a simple average, the report says so. The view on whether a pilot is justified is advisory; the decision rests with your company. The first three assessments are free; in return we learn from whatever you choose to share. Publishing any result is a separate, optional permission. See a sample report (illustrative, synthetic data).

Data handling

What happens to your file

What the software does

Reads your files on your machine and works in a temporary folder that is deleted when the run ends
Never modifies it (checked by an automated test)
Makes no network connections: checked by a source scan, a test, and a traced full run with zero network system calls
No third-party dependencies
Writes only the report you name (the older single-file commands also keep a small run log of file hashes)

Safeguards

Flags extra columns that look personal (emails, phones, names, addresses); the assessment ignores them and never stores them. Best effort: it can miss free text
Run log records version, settings and file hashes, never data rows. Hash-chained, so edits are detected. Tamper-evident, not tamper-proof
Reports label which data they were measured on

This website is separate. The early-access form sends what a visitor types to a Google Sheet operated by KPAppWorx. The “Try it” tool on the overview page reads a file inside the visitor’s browser and does not upload it. See the privacy policy.

What is missing

The honest checklist

Questions security and procurement teams usually ask, answered as they stand.

SOC 2, ISO 27001	None. No audit has started.
Independent penetration test	None.
Customer references	None. No production deployments.
Real-data accuracy evidence	None yet. Published figures come from invented data.
Integrations (SAP, Oracle, Snowflake, …)	None. CSV exports only.
Hosted service, single sign-on, roles	Not applicable today. There is no hosted service to sign in to.
Sub-processors	None for the engine, which runs on your machine. The website form uses Google.
Data residency and retention	Data stays where you run it. Udgass keeps nothing beyond the files you create. Udgass does not accept company data at present. If that is ever needed, signed written terms on storage, access and deletion come first.
Support and uptime commitments	None. One person, replies within a few days.
Contract terms, liability	Drafts only, not yet reviewed by a lawyer. Advisory use only. A pilot would be agreed in writing first.

What would change this, in order

Backtests on real historyWith three to five planning teams, shared only with their consent, whatever the result.
Head-to-head against your forecastPaid pilots using the comparison above.
Security work before any hosted versionIndependent penetration test, then a SOC 2 readiness exercise.
One read-only integrationFor one named system, chosen with a design partner.
Named referencesOnly from customers who agree.

Request the assessment Email the founder