Move dense embeddings and metadata between vector databases. Submit jobs through the UI or CLI, track progress, and resume interrupted transfers from checkpoints.
Start a transfer
Sign in at transfer.polign.com and choose where it runs:
| Mode | Setup | Data access |
|---|---|---|
| Customer worker — recommended | Open Create connection, run the setup script, and continue when your worker connects | Credentials, vectors, and checkpoints stay in your infrastructure |
| Polign hosted | Select Polign hosted in New transfer, then enter connection settings | Polign stores credentials encrypted and processes the vectors |
Before submitting:
- Prepare the destination for the source dimensions, IDs, and metadata types.
- Keep the source unchanged during the transfer and any resume.
- Check existing destination IDs: upserts replace matching records.
Transfers leave source data in place. They do not regenerate embeddings, copy index definitions, or convert incompatible metadata.
Connection setup · Supported databases
Try it locally
Requires Go 1.25+ on macOS or Linux. From the repository root:
Open http://127.0.0.1:23005. Choose New transfer → Start transfer to submit the demo's 1,000
four-dimensional vectors. The This server option runs them on your machine.
Output is saved in data/demo-vectors/. The demo makes no cloud requests.
To submit from another terminal:
./bin/vtransfer submit -file examples/demo-job.json -idempotency-key first-demo ./bin/vtransfer show JOB_ID ./bin/vtransfer events JOB_ID
Guides
Public getting-started guide · Local demo quickstart
- Customer worker setup: installation, connections, and recovery.
- Hosted and operator setup: UI credentials and configuration files.
- Provider catalog: schemas, authentication, and limits.
- Account setup and security: sign-in and credential boundaries.
- Deployment: release, update, and backup procedures.
- API and CLI: job and worker endpoints.
- Architecture: execution, retries, checkpoints, and audit storage.
Add a connector
Implement Source.Read and/or Sink.Upsert, then register a factory with
app.Run. The same connector works in the server and customer worker.
Author guide · Example · Contract · Contributing
make test # Go tests with race detection make test-ui # Generated worker script tests; requires Node make check # Go vet and JavaScript syntax check; requires Node
Most provider tests use protocol fixtures. See the catalog for live integration test setup.
License
Licensed under Apache 2.0. Bundled fonts retain their separate license.