Skip to content

Add Xata and SingleStore providers - #303

Merged
broisnees merged 1 commit into
nightlyfrom
providers-xata-singlestore
Nov 18, 2026
Merged

broisnees merged 1 commit into
nightlyfrom
providers-xata-singlestore

Conversation

@broisnees

Copy link
Copy Markdown
Collaborator
  • Xata (Postgres): paste an API key; every branch of every project in every organization is listed, and connecting fetches that branch's own credentials (…/branches/{id}/credentials), TLS on.
  • SingleStore (MySQL protocol): paste a Management API key; workspaces (by group) and starter workspaces are listed with their endpoints. The API never returns a database password, so it's asked once and remembered, like Supabase.
  • Hosts on *.xata.tech and *.svc.singlestore.com are recognised as these providers; SingleStore gets its brand mark, Xata a drawn X.

Both move to OAuth later: Xata's Keycloak allows dynamic client registration (verified), SingleStore needs a client ID from them. LiteFS isn't a hosted service and isn't added.

Unit tests cover the credential mapping; a bad key returns 401 on every endpoint used (checked against the live APIs), which puts the key form back. Not yet run against real accounts.

Both sign in with a pasted key for now. Xata: an API key lists every
branch of every project and connects with the branch's own credentials.
SingleStore: a Management API key lists workspaces and starter
workspaces; the API never returns a database password, so it is asked
once and kept, as with Supabase. Both can move to OAuth later: Xata
supports dynamic client registration, SingleStore needs a client ID.
@broisnees
broisnees merged commit 4ea7c90 into nightly Nov 18, 2026
@broisnees
broisnees deleted the providers-xata-singlestore branch November 18, 2026 16:39
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant