Backed by mandō

The universal
transfer protocol.

Conduit moves data from any source to any destination over 26+ protocols. One interface. Zero compromise. The API platform for transfers.

Start Transferring Free Live Demo →
Transfers / 24h
2,847,391
↑ 12.4%
Avg. Latency
23ms
↓ 8.1%
Protocols Active
26
— stable
Success Rate
99.97%
↑ 0.02%
Data Moved
4.2 PB
↑ 18.7%
Active Connections
18,442
↑ 6.3%
Core Platform

Every transfer primitive, one interface

Conduit maps every flag to a first-class capability. No wrappers. No abstractions. Pure transfer.

→

Output Engine

Write response data to any destination with -o. Use -O for remote-name inference. Automated path resolution included.

↩

Redirect Chain

Follow 301/302/303/307/308 redirects automatically with -L. Set max depth with --max-redirs. Never lose a resource.

▤

Header Forge

Inject arbitrary headers with -H. Inspect response headers with -I. Full control over every byte in your request.

⇅

Method Router

Override HTTP methods with -X. GET, POST, PUT, DELETE, PATCH, OPTIONS — route any verb to any endpoint.

⊞

Payload Builder

Submit form data with -d, multipart uploads with -F, or raw JSON with --json. Every content type, handled.

🔐

Auth Layer

Basic, Digest, NTLM, Negotiate, Bearer — authenticate with -u or --oauth2-bearer. AWS SigV4 supported natively.

🍪

Cookie Vault

Read cookies with -b, persist them with -c. Full Netscape cookie jar compatibility. Session state, solved.

📊

Write-Out Analytics

Extract metrics with -w: response time, DNS lookup, TLS handshake, size, speed. Format any variable into structured output.

♻️

Retry Engine

Automatic retries with --retry and exponential backoff. Set --retry-max-time and --retry-delay for fine-grained control.

Protocol Matrix

26+ protocols, one binary

Every protocol battle-tested across billions of transfers. Full TLS support on all secure variants.

HTTP ● Active
HTTPS ● Active
FTP ● Active
FTPS ● Active
SCP ● Active
SFTP ● Active
IMAP ● Active
IMAPS ● Active
POP3 ● Active
POP3S ● Active
SMTP ● Active
SMTPS ● Active
LDAP ● Active
LDAPS ● Active
MQTT ● Active
RTSP ● Active
DICT ● Active
TFTP ● Active
TELNET ● Active
GOPHER ● Active
SMB ● Active
SMBS ● Active
WS ● Active
WSS ● Active
RTMP ● Active
FILE ● Active
Workflow

Three steps to universal transfer

01

Target

Point Conduit at any URL. HTTP, FTP, SCP, SMTP — the protocol is auto-detected from the scheme. No configuration needed.

02

Configure

Set your method, headers, auth, payload, and timeouts. Every option composable. Every combination valid.

03

Transfer

Data moves. Conduit handles redirects, retries, compression, cookies, and connection reuse automatically.

Request Builder

Compose your transfer

Build, preview, and execute — all from one interface.

conduit — command preview 
conduit -L -H "Authorization: Bearer tok_live_abc123" https://api.example.com/v1/users
Live Demo

See Conduit in action

Real commands. Real output. Real transfer.

conduit — session
$ conduit -I https://api.conduit.dev/status
HTTP/2 200
content-type: application/json
x-request-id: req_7f3a9b2c
$ conduit -s -o data.json https://api.conduit.dev/v1/metrics
% Total % Received Avg Speed Time
100 4218 100 4218 0 182k 0:00:00
$ conduit -X POST -H "Content-Type: application/json" -d '{"name":"conduit"}' https://api.conduit.dev/v1/transfers
{"id":"txn_8k2m","status":"created","protocol":"HTTPS"}
$ conduit -u admin:secret --retry 3 -L https://api.conduit.dev/v1/health
{"status":"healthy","uptime":"99.97%","protocols":26}
$ conduit -w '%{http_code} %{time_total}s %{size_download}B\n' -s -o /dev/null https://conduit.dev
200 0.023s 14218B
$ conduit -F "[email protected]" -F "project=conduit" https://api.conduit.dev/v1/uploads
{"upload_id":"upl_9x3n","size":2847391,"status":"complete"}
█
Performance

Transfer metrics, in real time

Every variable from -w write-out, visualized.

time_namelookup
0.004s
time_connect
0.012s
time_appconnect
0.031s
time_starttransfer
0.042s
time_total
0.058s
speed_download
245 KB/s
size_download 14,218 B
size_header 412 B
http_code 200
num_redirects 0
ssl_verify_result 0 (OK)
http_version 2
0
protocols
Supported natively
0
.97%
Transfer success rate
0
PB
Data transferred monthly
0
ms
Median response latency
Why Conduit

The category leader

Side-by-side, Conduit outperforms every alternative on the metrics that matter.

Capability Conduit Competitor A Competitor B Competitor C
Protocols supported 26+ 3 8 12
HTTP/2 & HTTP/3 ✅ HTTP/2 only ❌ HTTP/2 only
Follow redirects ✅ (configurable depth) ✅ ✅ Limited
Auth methods 7+ (Basic, Digest, NTLM, etc.) Basic only Basic + Bearer 3
Connection reuse ✅ ❌ ✅ ❌
Write-out metrics 50+ variables None 5 variables None
Retry with backoff ✅ ❌ ✅ Manual only
Price Free tier $29/mo min $99/mo min Enterprise only
Live

Transfers never sleep

Pricing

Plans that scale with you

Start free. Upgrade when your transfer volume demands it.

Starter
$0/mo

For developers exploring the platform.

  • HTTP/HTTPS transfers
  • -o output to file
  • -L follow redirects
  • 100 transfers/day
  • Community support
Get Started
Most Popular
Pro
$29/mo

For engineers building integrations.

  • All 26+ protocols
  • -X custom methods
  • -d / -F / --json payloads
  • -u all auth methods
  • -w write-out analytics
  • --retry with backoff
  • Request Builder UI
  • Unlimited transfers
Start Pro Trial
Team
$79/seat/mo

Transfer infrastructure for the org.

  • Everything in Pro
  • -b/-c cookie management
  • -T upload pipelines
  • --connect-timeout SLA rules
  • Performance dashboard
  • Audit logs & SSO
  • Team analytics
Start Team Trial
Enterprise
Custom

Mission-critical transfers at any scale.

  • Everything in Team
  • -k advanced TLS config
  • -A user-agent management
  • Dedicated transfer cluster
  • Custom SLA & uptime
  • On-premise deployment
  • 24/7 dedicated support
Contact Sales
Social Proof

Trusted by high-throughput teams

★★★★★

"We replaced four different HTTP libraries with Conduit. One interface for REST APIs, file downloads, and webhook delivery. The write-out analytics alone saved us from shipping a custom metrics pipeline."

Saskia Starling VP of Engineering, DataPipe Inc.
★★★★★

"The retry engine with exponential backoff is production-grade out of the box. We process 800K transfers daily through Conduit. Zero custom retry logic. Zero downtime."

Raj Mendoza SRE Lead, TransferGrid
★★★★★

"I've been building API integrations for 12 years. Conduit's multipart upload with -F and the cookie vault changed how I think about stateful workflows. This is the final transfer tool."

Zara Lee Principal Engineer, StackBridge
★★★★★

"26 protocols under one roof. We use Conduit for HTTP APIs, SFTP batch uploads, and even SMTP notifications. Our infrastructure team went from 15 tools to one."

Daniel Kovacs CTO, OmniRoute Systems
What's New

Shipping relentlessly

v8.4

HTTP/3 + QUIC Native Support

Use --http3 for automatic HTTP/3 with graceful fallback. QUIC-powered transfers now available on all plans.

Feature Performance
v8.3

Variable Expansion Engine

Command-line variables with --variable and --expand-url. Templated requests without shell interpolation. Supports trim, json, url, and b64 functions.

Feature
v8.2

Trace Config & Trace IDs

Fine-grained trace output with --trace-config. Tag every trace line with transfer/connection IDs via --trace-ids.

Improvement
FAQ

Questions? We've got answers.

How does Conduit handle authentication?

Conduit supports Basic (-u user:pass), Digest (--digest), NTLM, Negotiate/SPNEGO, Bearer tokens (--oauth2-bearer), and AWS SigV4 (--aws-sigv4). Authentication is protocol-aware and secure by default.

Can I use Conduit with APIs that require cookies?

Yes. Use -b cookies.txt to send cookies and -c cookies.txt to save received cookies. Full Netscape cookie jar format support. Session state persists between requests.

What happens if a transfer fails?

Use --retry N for automatic retries with exponential backoff. Combine with --retry-max-time and --retry-delay for precise control. Conduit retries on timeouts and 5xx errors by default.

How do I measure transfer performance?

Use -w with over 50 variables: time_total, time_connect, speed_download, size_download, http_code, and more. Output as JSON with %{json}.

Does Conduit support file uploads?

Absolutely. Use -T file for PUT uploads, -F "field=@file" for multipart POST uploads, or -d @file for raw body payloads. Works across HTTP, FTP, SFTP, and SCP.

Backed by mandō

Lyst Drift Locus Repliq Portage Voidal Scaffold Vøid Imprint Concat Stratum Folio Topline Tailstream Sieve Seekr Rewrite Trellis Sortable SINGULR Census Slice Morph FanOut Argonaut Reverb Formatik Epoch Solstice IDENT Signum Quorum Pulsar Overseer Terminus PURGE Dispatch Sotto Limelight Persist Vantage Canopy Attaché Détaché Tether Aegis CLAIMR Cohort Archivex Deflate Unravel ArcVault XTRAKT AFFIRMATIV Conduit Fetch VaultLink Teleport DeltaSync Heartbeat Hopscotch Resolver Namesake Uplink CONNEX Callsign Milieu Propagate Sourcery Persona SEVER Chronicle Codex Relevance Resolv Nomenclature MAGIQ Intrinsic Diverge Patchwork VIGIL Breeze Cadence Kronos Atelier SUPRA Mandate Turnkey Accession Reforge Collective PipeForge Netweave Panoptik Substrate Repose Verity FAULTR Provenance Chrono