Skip to main content
Platinur v1 deliberately supports a small native catalog. Every source shown in the portal is owned, operated, and tested by Platinur through the same secure source lifecycle. A driver or unfinished adapter in the codebase does not make another source available.

​
Native v1 sources

Each source writes to its own ClickHouse database with a raw_ prefix. For example, a source whose target is billing lands in raw_billing. You can inspect the discovered schema and choose which tables to load before syncing.

​
Source setup

Open Integrations → New Source, choose a source, and follow its setup guide. Platinur asks only for the fields that source needs. The source form does not display a generic numbered workflow. After the connection is saved, its page contains:
  • Config for connection settings and activation;
  • Schema for discovery and table selection;
  • Runs for durable connection tests, discovery, and sync history; and
  • Schedule for database sources that refresh automatically.
Connection tests, discovery, manual syncs, and scheduled syncs are also visible in Monitoring.

​
Security boundary

PostgreSQL and MySQL must be reachable from the Platinur account worker over a TLS-protected public endpoint. PostgreSQL uses certificate and hostname verification with verify-full. MySQL verifies the certificate and server identity using the worker’s trusted CA bundle. Plaintext database sessions are refused. Secrets are stored in the workspace secret store and are never returned by the portal. Use a dedicated read-only source user and grant it access only to the schemas and tables Platinur should load.

​
Deferred sources

SQLite, generic REST, other vendor API presets, Google Drive, Google Analytics, Google Ads, and Google Search Console are not available for new v1 sources. They remain outside the catalog until their customer flow and real lifecycle certification are complete. Customer-owned Airbyte Cloud monitoring is planned as a separate integration. Airbyte will own the individual SaaS connectors and source credentials; Platinur will monitor selected Airbyte connections and model the data they write into the attached ClickHouse warehouse.

​
Failures and recovery

A failed connection test, discovery, or sync becomes a durable run rather than a transient toast. Open the source’s Runs tab or Monitoring for the sanitized reason and next action. Correct the connection or source availability issue, test again, then retry discovery or sync. Credentials and provider response bodies are never written to run logs.