Availability
TurtleTech Data is a manually provisioned limited preview. The Tardigrade tt
client has no
unauthenticated public installer, and a TurtleTech ID alone does not activate
storage. Request access at
info@turtletech.us before following either path.
Tardigrade native client (preferred)
Once TurtleTech Data is provisioned for your account, the supported Tardigrade
tt build for your platform is listed on your subscription page in the
TurtleTech dashboard, with the checksum to
verify it against. Download links are issued to your account and expire; the
archives are not served openly.
Verify and install, then use the native TurtleTech Data protocol, which is the default:
sha256sum tt-x86_64-unknown-linux-gnu.tar.gz
tar -xzf tt-x86_64-unknown-linux-gnu.tar.gz
install -m 0755 tt-x86_64-unknown-linux-gnu/tt ~/.local/bin/tt
tt --version
tt auth login
tt init
tt add data/training-set/
tt save "baseline dataset"
tt history
The Tardigrade protocol is checkpoint-first and chunked. DVC is not required for this TurtleTech Data workflow.
DVC compatibility
This path is for an established DVC repository or a staged migration. Install DVC with S3 support using the official DVC installation guide, then use the TurtleTech proxy credentials issued during provisioning. Keep access keys in the local DVC config so they are not committed:
dvc remote add -d ttech s3://data
dvc remote modify ttech endpointurl https://dvc-s3.turtletech.us
dvc remote modify --local ttech access_key_id YOUR_ACCESS_KEY
dvc remote modify --local ttech secret_access_key YOUR_SECRET_KEY
The public hostname above is the compatibility proxy. Do not substitute the retired pre-launch hostname or an underlying provider endpoint.
Push data
dvc add data/training-set/
dvc push
Pull on another machine
git clone your-repo
cd your-repo
dvc pull
Troubleshooting
Check the proxy health endpoint and the local remote configuration without printing secret values:
curl --fail https://dvc-s3.turtletech.us/health
dvc remote modify --list ttech
A 403 Access Denied response is not a quota diagnosis by itself. It can also
mean that a credential is invalid, disabled, or belongs to a different access
path. Contact support with the timestamp and command name, but never send a
secret key by email.