Not multi-user-safe in v0.1.0. A database-DDL authorization bypass is open: any authenticated user can CREATE/DROP DATABASE regardless of privileges (verified). This profile hardens transport and identity for a single-operator host only. Do not use it for shared, multi-user, or cloud deployment until a fix lands and is verified. See Beta status.
For any listener beyond loopback: TLS required, SCRAM, a unique password, and explicit capacity. The server refuses to start without all three — missing TLS, the built-in password, or auth none on a remote bind each fail closed with a remediation message.
plomid-server \
--host 0.0.0.0 \
--auth scram \
--password "$PLOMID_PASSWORD" \
--tls --tls-cert /etc/plomid/cert.pem --tls-key /etc/plomid/key.pem --tls-required \
--max-connections 100 \
--statement-timeout 30s \
--idle-in-transaction-timeout 60sWithout TLS yet (trusted LAN or container network only), substitute the explicit opt-in — authentication still required, transport unencrypted:
plomid-server --host 0.0.0.0 --password "$PLOMID_PASSWORD" --allow-remote-plaintextPrefer TLS as soon as it is available. Confirm tls_required=true and allow_remote_plaintext=false in the effective_config log.