sgr command-line client is 'hosting agnostic' and pairs well with your own
Splitgraph Engine hosted wherever you prefer to run your apps.
Splitgraph also offers a public-facing Splitgraph service, with a catalog, Splitgraph engine, the DDN, docs, and more.
The catalog is a webapp with its own web UI that makes it easy to graphically
manipulate repositories with a browser, perform searches, upload datasets, etc.
In cases when it's preferable to use the CLI, consider using
|Add a remote Splitgraph registry to .sgconfig with default parameters
|Register the user on a Splitgraph registry.
|Log into a Splitgraph registry with username/password.
|Log into a Splitgraph registry using existing API keys.
|Output an up-to-date access token for a remote.
|Run SQL on or connect to the Splitgraph Data Delivery Network.
|Query a Splitgraph REST API.
|Upload a README to a Splitgraph repository.
|Upload a description to a Splitgraph repository.
|Upload a metadata file to a Splitgraph repository.
|Search for a repository on the Splitgraph registry.
|Dump a Splitgraph catalog to a YAML file.
|Load a Splitgraph catalog from a YAML file.
|Trigger an ingestion job for a repository.
|Get job statuses for given repositories.
|Get ingestion job logs.
|Upload files to Splitgraph.
|Download query results from Splitgraph.
|List all Splitgraph Cloud data plugins.
|Generate a splitgraph.yml stub file for a given plugin
|Validate, merge and output project file(s)
|Generate a starter Splitgraph Cloud project from a seed.
|Start tunnel to query a private data source.