Skip to content
portward

Sources

Your data stays where it lives.

Portward connects to your databases, APIs and files in their own systems and reads only what a permitted task needs. The people asking questions never see or handle the credentials.

Connect a sourceHow sources work
DatabasesBusiness appsDocumentsPort authorityTeam knowledgeClaudeCodexMCPPort checklistPersonAgentDataOperationDestinationDefinitionUsageEvidenceCurrentv4 governedContext deliveredGovernedCustomer emailsHeldRevenue, SepClearedHeldWhy did revenue change?Proposed correction

01Kinds of source

Four families, one set of rules.

Each family has its own boundary, the smallest unit you can allow or refuse. The meaning of a source, a credential and a rule is the same across all of them.

SQL databases and warehouses

Where you draw the line
Database, schema, table or view, with row and column restrictions where the source supports them.
What Portward reads first
Tables, views, columns and declared keys that the connection is allowed to see.

REST APIs

Where you draw the line
An approved origin, with the paths, methods and parameters you allow.
What Portward reads first
The operations you declare. Credentials are never forwarded to an origin you did not approve.

Object storage

Where you draw the line
A bucket and a prefix.
What Portward reads first
Object names and metadata. Listing a file does not grant permission to fetch its contents.

Files and documents

Where you draw the line
A collection, a folder or a single document.
What Portward reads first
File metadata and structure. Content is read only from the documents you select.

02Adding a source

Connect once. Everyone you permit can use it.

A source is registered one time. People reuse it through their own identity, and a failed or rotated credential never makes the source or its knowledge disappear.

1. Connect

Enter the connection details once. The credential goes into a vault and is used only on paths you authorized. It never appears in logs, errors or anything sent to an assistant.

2. Read the structure

Portward reads what the connection is allowed to see, such as schemas, tables and columns. This first pass uses no AI model, and it reads structure, not your rows.

3. Set the rules

Decide who may use the source and what must stay out of reach. The rules belong to the source, so they apply wherever it is used.

4. Add what your team knows

Attach definitions, usage notes and documents that explain the source. Reviewed knowledge is labelled Governed, and the rest stays Provisional until someone approves it.

03Which connectors

A connector is offered when it is proven, not when it is named.

Portward is in beta, and connectors are verified one at a time. The app shows the current status of each one, so this page does not list names it cannot back up.

Connector status in the app

  • Available

    Every step, from connecting to enforcing an exclusion, has a passing test against that connector.

  • Available with limitations

    Every step is proven, and the connector states what it cannot do yet.

  • In validation

    The connector exists, but something is still unproven. You cannot select it until it is.

Start with one source.

Connect the database or the files you ask about most, and see what your assistant can do when it knows what the columns mean.

Get startedHow credentials are protected