The missing storage layer for CI, agents, and release artifacts.

Git keeps your source. CI and agents produce the output. Blob Yard gives every build, binary, dataset, log bundle, and generated file a durable path to the person or system that needs it.

Upload from the terminal, CI, or an agent. Store it durably and privately. Hand it off with scoped, revocable access.

Move one real artifact into Blob Yard.

Install CLI Open dashboard

Live CLI session

blobyard upload ./dist/release.zip --path releases/release.zip

Scoped transfer grant created

Uploading100%

Blobyard URI: blobyard://workspace/project/releases/release.zip?version=1

blobyard share blobyard://workspace/project/releases/release.zip?version=1 --expires 7d

Share URL: https://blobyard.com/s/<public-share-capability>

Revocable share expires in 7 days

Stored file remains unchanged

The problem

Your team already has file storage. That is the problem.

Builds end up in Slack. Binaries creep into Git. LFS quotas break CI. S3 turns a simple handoff into infrastructure. Blob Yard gives those files one developer-native route.

Before Blob Yard

The handoff is improvised.

GitKeeps source history. It should not become artifact storage.
Git LFSHelps large files ride along, until bandwidth and quotas break CI.
S3Stores anything, but makes every handoff a bucket, a policy, and a credential.
DropboxShares files with people. It does not belong inside CI.
SlackWhere files get posted once and disappear.

With Blob Yard

One durable path instead.

Blob Yard is the missing route between the thing that produced the file and the person or system that needs it. Expiring shares control access without deleting the stored file.

01
Producers send the file
Upload from the native CLI, trusted GitHub Actions, local MCP server, or stable API.
02
The source stays durable
Blob Yard verifies it, stores it privately, and records the version and audit event.
03
People get controlled access
Create a scoped share, inbox, preview, or download without changing the stored file.

Choose the access path:

What moves through it

One route for every file your software process creates.

The same durable storage and scoped handoff, whatever produced the file.

01 / Team handoff

Stop losing release files in chat.

One durable source. Controlled access. Clear version. No more “which one?”

# release-handoffHandoff the current release build.

12 members

Maya9:02 AM

Which build is current?

Alex9:03 AM

I thought this was it.

release-final.zip45.2 MB · ZIP

Maya9:06 AM

Wait, no. I think this one.

release-final-2.zip45.2 MB · ZIP

Alex9:09 AM

Here is the source of truth.

blobyard.com/s/<share-capability>

02 / CI workflowrelease.ymlRun #481

Build release

Exchange GitHub OIDC identity

Upload dist/release.zip

blobyard://acme/releases/release.zip?version=12

Scoped CI uploads with no permanent storage credential in the runner.

03 / Agent and MCP

Give generated output somewhere durable to go.

The local MCP server gives agents the same bounded upload and inspection path as a developer.

agent / tool output

blobyard_uploadreport.pdf · 8.4 MB

blobyard://acme/research/reports/report.pdf?version=3 Stored and inspectable

04 / Customer upload inbox

Receive files without opening the workspace.

A bounded inbox accepts the requested log bundle, then closes on schedule.

Support logsZIP or TAR · 2 GB maximumUploads close tomorrow at 17:00

05 / Browser preview

preview-7f3c.blobyard.dev

Release candidate

Static output served from an isolated preview origin.

Static publishing, backed by Blob Yard

Give built output a stable public Yard.

Publish documentation, Storybook, dashboards, and static applications from the same durable project storage. Each named Web Yard gets a stable blobyard.app address and a retained deploy history.Explore Web Yards

publish static output

blobyard deploy ./apps/docs/dist --yard documentation --public

Web Yard: documentation
URL: https://documentation-123456789-main.blobyard.app
Deployment URL: https://documentation-0123456789-main.blobyard.app
Status: live

PublishUpload a prebuilt static directory.
VerifyKeep every deploy immutable and inspectable.
Roll backRepoint the stable address to an earlier deploy.

Engineered for the handoff

Durable storage without turning every file into infrastructure.

One native Rust binary

Install a verified standalone CLI with no npm, npx, or runtime dependency tree.

Share any file in seconds

Store any file durably, then create a revocable link when you want to share it.

Expiring links and guest inboxes

Send a revocable download or receive files through a controlled upload inbox.

Managed storage without IAM pain

Keep files in durable private storage while scoped transfer grants protect bucket credentials.

Audit trails from day one

Keep a durable record of uploads, downloads, sharing, and revocation.

Secretless GitHub Actions

Use scoped GitHub OIDC sessions instead of keeping a permanent CI upload secret.

Security by architecture

No permanent storage credentials. Ever.

Stored files are durable. Blob Yard gives each user, agent, CLI, workflow, and public capability only the access required for its next operation.Read the security model

No permanent storage credentials

Storage keys stay at the server boundary. Clients receive only scoped grants.

Revocable capability links

Access links can expire or be revoked without deleting the file they point to, and tokens are stored only as hashes.

Audit from the first action

Uploads, downloads, sharing, CI, billing, and retention keep actor-aware evidence.

Bonus utility

Share a secret. Exactly once.

Send a password, API key, recovery code, or private note with client-side encryption and single reveal.

Create a one-time link

Move one real artifact to Blob Yard.

Pick the build, dataset, log bundle, screenshot, or agent output your team currently hands off through a repo, chat, shared folder, or one-off bucket. Upload it with the CLI, share it with scoped access, and keep the stored source and audit history.

Install the CLI See pricing