The criteria live in documents
Policies, operating standards and contract terms sit in a document repository. Half of every answer is finding and reading that document.
PAASUP DNA · Knowledge analytics
Documents and data
in a single question.
Whatever must be masked stays masked wherever the query runs. When you outgrow it, PAASUP DIP takes over.
After the consultation we run a PoC on one data source.
Why it takes so long
Documents here, databases there, masking somewhere else.
One question means three systems.
The numbers live in the database
How many, how much, right now: that is in the database. Getting the number means going through someone who writes SQL.
Masking is set up per system
When each system masks personal data its own way, the same person sees different values depending on the path they took.
Promise
A question that used to cross three systems ends in one.
Document repository, data catalog and de-identification policy live in one environment. The person asking does not need to know which system holds the answer.
Documents and the database answer together
Documents, unstructured and structured data live in one repository, one catalog, one question box. One question gets an answer from documents and the database together, with the source file name, page and the SQL that ran.
Whatever must be masked stays masked wherever the query runs
Personal data is masked at read time by a policy set once. Document queries and SQL results fall under the same policy. The original is never touched.
People and AI agents see only what they are allowed to
Viewing, search, SQL and ETL all pass through the same permission gate. Run the same query as two users with different permissions and different values get masked.
Real screens
Shown on real screens.
Captured on a demo tenant. All personal data is fictitious.
Documents + data in one conversation
The criterion from the document, the current figure from the table. One answer carries the source file name, page and the SQL that ran.
Content filter bindings
doc:// document paths and data:// table columns share one de-identification policy. Exceptions only for named subjects. Anyone who is not an exempt subject sees masked values only.
Structured-analysis notebook (Korean UI)
Several SQL cells in one document, each rendered as a different chart (line, bar, pie). Switch chart types per cell and try them out.
MD dashboard (Korean UI)
The same data laid out as KPI, trend, comparison and share cards in one dashboard document. The document itself is the dashboard.
When scale grows
Large-scale processing is delegated to PAASUP DIP.
Batch, virtualization, streaming and LLM serving move to the platform below, and permissions and policy carry down as is. Who can see what does not change. See PAASUP DIP →
Getting started
Start with one data source.
-
1
Consultation
We pick one data source and one document repository.
-
2
PoC
Run the same question under two permission sets within that scope. That is where the PoC ends.
-
3
Grow
Add sources and repositories as you need them. Permissions and policy follow the same way.
Consultation
Tell us which question
you want to ask in one go.
Share the questions you ask often and where their answers live in documents and data. We will reply with a scoped PoC.
- One or two questions that take too long to answer
- Where the related documents and databases are
- The kinds of information that must be masked (personal data and so on)