Peliqan screenshots

An all-in-one data platform for small teams: connectors, a built-in warehouse, SQL and Python.

Peliqan

One connection form template across seven databases

Peliqan uses the same form-plus-info-panel modal for every database, with per-connector defaults and an Invite button to hand the job to someone who has the credentials.

B2BactivationMar 2025

01

BigQuery

A service-account key, a region and a side panel that says where to get the key.

Peliqan: BigQuery
  1. 1

    Name prefilled (working)

    Connection name defaults to "BigQuery", one less decision.

    Default effect

  2. 2

    Where to get the key (working)

    The info panel gives the Google Cloud IAM path to create and download a JSON key.

    Contextual help

  3. 3

    Paste JSON in a one-line box (not working)

    "Open the file, copy the full json and paste it here" into a single-line input instead of offering a file upload.

    Reduce friction

  4. 4

    Format example (working)

    "For example us-central1" shows the expected value under the field.

    Contextual help

  5. 5

    Invite a colleague (working)

    Whoever opens this form often doesn't hold the credentials; Invite lets them hand it to someone who does.

    Human in the loop

  6. 6

    Save without a test (not working)

    Save and Invite have the same weight, and there is no "Test connection" before saving.

    Error prevention

02

Postgres

The same template with username, password, host, port and an optional target database.

Peliqan: Postgres
  1. 7

    Default port filled (working)

    5432 is already in the Port field.

    Default effect

  2. 8

    Host with no hint (not working)

    No example of the host format and nothing about IP allowlisting, the usual reason a Postgres connection fails.

    Contextual help

  3. 9

    Optional field explained (working)

    "Optional, only set if this connection will be used as a DW Target" tells you when you can skip it.

    Clarity

  4. 10

    Info panel repeats the field (not working)

    "Default port: 5432." is all the side panel says, and the field already shows it.

    Signal vs noise

03

Redshift

Redshift gets its own default port and a side panel that explains what happens after Save.

Peliqan: Redshift
  1. 11

    Connector-specific default (working)

    Port is 5439 here, not the Postgres 5432, so the template adapts per database.

    Default effect

  2. 12

    Generic first line (not working)

    "Select a connector" when you've already picked Redshift shows the copy is shared, not written for this screen.

    Personalization

  3. 13

    What Save will do (working)

    "All schemas, tables and columns will be discovered" sets expectations for the next step.

    Expectation setting

04

Snowflake

The longest form, with a side panel full of SQL commands for warehouse and role setup.

Peliqan: Snowflake
  1. 14

    Explains the defaults (working)

    The panel says Peliqan uses the user's default warehouse and gives the account-name format "xx12345.eu-central-1".

    Contextual help

  2. 15

    SQL as grey prose (not working)

    ALTER USER and SELECT commands are set in body text with no code style or copy button, so they're hard to grab.

    Recognition over recall

  3. 16

    One field, two meanings (not working)

    "Password / private key pass phrase" with a long hint; an auth-method choice would be clearer.

    Clarity

  4. 17

    Optional explained again (working)

    The same DW Target helper as Postgres, so the pattern is learnable across connectors.

    Consistency and standards

05

Trino

Trino's form drops the required marks on username and password but leaves the port empty.

Peliqan: Trino
  1. 18

    Auth not forced (working)

    Username and password have no asterisk here, so the form follows how this database works.

    Flexibility and efficiency of use

  2. 19

    Required port, no default (not working)

    Unlike Postgres and Redshift, Port is required and empty.

    Default effect

  3. 20

    Says why the field exists (working)

    "Peliqan will connect to this database for discovery" explains the optional field.

    Reason-giving

  4. 21

    Info panel says nothing (not working)

    "Connect your Trino server to Peliqan." repeats the title.

    Signal vs noise

06

Microsoft Fabric DWH

Fabric adds SSL and auth-type settings, with the auth choice placed after the fields it changes.

Peliqan: Microsoft Fabric DWH
  1. 22

    Hints depend on a later choice (not working)

    "Enter Client ID when Service Principal is used" refers to Auth type, which you only pick at the bottom.

    Progressive disclosure

  2. 23

    Port 1433 prefilled (working)

    The SQL Server default port is filled in.

    Default effect

  3. 24

    SSL off here, on for MS SQL (not working)

    "Enforce ssl" is off by default on Fabric but on for MS SQL Server in the same app.

    Consistency and standards

  4. 25

    "Make a choice" last (not working)

    Auth type is required but sits at the end with a placeholder that doesn't hint at the options.

    Progressive disclosure

07

MS SQL Server

Same fields as Fabric, with SSL switched on by default.

Peliqan: MS SQL Server
  1. 26

    Panel repeats the port (not working)

    "Default port: 1433." again uses the help panel for something the field already shows.

    Signal vs noise

  2. 27

    Same optional pattern (working)

    The DW Target helper appears in the same place on every connector.

    Consistency and standards

  3. 28

    Secure default (working)

    "Enforce ssl" is on, so the safe option needs no action.

    Default effect

Takeaways from Peliqan

  1. A shared form template with a help panel scales to many connectors, but write the panel per connector or it fills up with filler like "Default port".
  2. Put the choice that changes other fields (auth type) first, and prefill every known default, including ports.
  3. Offer an Invite path in credential forms: the person setting up often isn't the one holding the keys.