avenAsset systems
for the creative web.
Get in early
Independent asset infrastructureVol. 01 / Private beta

For the things you’re making.

Good files.
Go places.

An independent home for the images, files, and little details behind your next idea. Built around clear paths and lighter workflows.

Request an invitation Open the field notes
Less to manage.
More to make.
Study 001The life of a file ↗
Paper files travelling on a sculptural citron track, with graphite routing marks and a cobalt envelope.
Origin → Policy → DeliveryObjects in motion.

Files, with a little more direction.

DeliveryCacheImagesStorage
↓

01 / The building blocks

The internet runs
on little things.

A font. A photograph. The files that make a product yours.
Give them a system with a little more care.

Small files.
Big possibilities.
A / Asset delivery

From a working file
to a working world.

Give every release its own path. Keep public links clear, and let your next idea find its way out.

Follow the delivery path ↗
Reference architectureVersioned paths / Standard HTTP
B / Edge caching

A good memory.
With clear boundaries.

Keep the files that stay. Recheck the ones that change.
A cache policy is part of the design.

response.headersCache-Control: public, max-age=31536000, immutableNew version. New URL. A clear contract.
Read the caching notes ↗
C / Object storage

A place for
the possibilities.

Project-first storage is on the drawing board. A quieter way to organize what comes next.

In development
Three tactile photographic print proofs showing the same cobalt paper sculpture in different crops.
Study 002 / One image. A few new perspectives.
D / Image workflows

Every pixel,
a place to be.

A responsive world needs more than one size. We’re exploring a workflow for useful crops, considered formats, and images that fit.

cover-640.webp → cover-1280.webpPlanned workflow · No live processing endpointA few notes on images ↗

02 / The developer’s desk

Open the hood.
It makes sense.

Standard HTTP. Readable paths. Nothing hidden behind a clever name. Start with the tools you know and keep the details in sight.

Inside the toolkit
A small request, with clear intentions.
Inspect a release
Demonstration
curl --head https://assets.example/releases/site-v1/styles.css
content-type
image/webp
cache-control
public, immutable
etag
"a-new-release"

Illustrative headers / No live API call

03 / Before you go

A few good
questions.

What is Aven?

A private beta project exploring a more considered home for digital assets: delivery, caching, image workflows, and project-first storage. Public guides and reference files are available now.

How does early access work?

The platform is invitation-only while the product takes shape. The access page is the place to start.

Can I try the developer API?

The API is still in development. The field notes include clearly marked request examples and a real reference manifest you can inspect.

Can I keep using my own tools?

That’s the direction. Standard HTTP, readable paths, and clear release boundaries keep a workflow understandable and portable.

There’s room for your next idea.

Shall we make
something move?

Request an invitation