Docs › Connecting data
Connecting data
Uploads
| Format | What happens |
|---|---|
| CSV, Parquet | one table per file; messy CSVs are loaded on the most permissive reader that yields rows, and the upload message says which |
Excel (.xlsx) | one table per sheet |
| PDF, Markdown, text | indexed as a document, searched by passage |
Upload limits per plan: Explore 5 MB, Analyst 20 MB, Team and Business 100 MB for CSV and Parquet (Excel 50 MB, because a workbook takes far more memory than its file size). Documents (PDF, text, Markdown) have their own limit: Explore 20 MB, Analyst 50 MB, Team and Business 200 MB. The browser checks a file's size before sending it, and documents are indexed in the background — the data panel shows "indexing…" with progress until the file is searchable. Scanned PDFs are read by OCR (Hungarian and English, on the server, no external service): only pages without a text layer are OCR'd, and every passage that came from a scan is marked "from OCR" in the document row and beside the cited passage — check figures read from a scan against the original.
Uploaded files are stored as-is and checked by hash; ProLyt never rewrites them. If a file with the same name already exists you are asked whether to keep both or replace.
URL sources
A table can be ingested from an https URL that serves a CSV. The source stays listed in the data panel with a refresh button; a refresh that fails shows the error on the source and, after repeated failures, disables itself until you retry.
Connecting a database
Workspace owners connect a database on the Workspace page under Data & sources → Connected database. One database per workspace.
- PostgreSQL is supported today. MySQL and SQL Server are on request (their drivers are not shipped in the hosted service).
- Queries run live against your database; ProLyt stores the connection details encrypted and indexes the table and column names for search. It does not copy your tables.
- The connection is tested before it is saved: a wrong password, an unreachable host or a missing database is refused with the reason, and nothing is stored.
- On the hosted service the database must be reachable from the internet and the connection uses TLS (ProLyt adds
sslmode=require). Private addresses —localhost, LAN ranges, VPN names — are refused with a message saying that this needs an on-premise installation. - SQLite and DuckDB file URLs are refused in every mode.
Use a read-only database user
ProLyt's query guard refuses INSERT, UPDATE, DELETE, DROP, CREATE, ALTER and similar statements before they reach your database. It does not block read-only functions a database may expose (for example functions that read files on the server). The permissions of the database user are the primary control, so connect with a user that can only read:
`` CREATE ROLE prolyt_ro LOGIN PASSWORD '...'; GRANT CONNECT ON DATABASE yourdb TO prolyt_ro; GRANT USAGE ON SCHEMA public TO prolyt_ro; GRANT SELECT ON ALL TABLES IN SCHEMA public TO prolyt_ro; ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO prolyt_ro; ``
Grant only the schemas you want ProLyt to see. What the user cannot read, ProLyt cannot read either.
On-premise installations
An on-premise ProLyt runs inside your network, so private database addresses are allowed there and the database can stay unreachable from the internet. Air-gapped installs work with open-source models on your own hardware. See Private and regulated data.