Managing digital assets often becomes more complicated than it should be.
A project may use one service for file uploads, another for image optimization, object storage for the original files, custom scripts for versioning, and a CDN for delivery.
This works, but it creates a fragmented workflow.
I’m building Smooth Bundle to bring these steps into one place.
The problem
Assets are rarely just static files sitting in a folder.
Developers need to:
upload them from different sources,
optimize images and generate variants,
organize files across projects,
manage versions and environments,
protect selected assets,
publish updates without breaking existing URLs,
and deliver everything efficiently to websites, apps, and CMS platforms.
Most existing services focus on one part of this process. Smooth Bundle is designed around the full asset workflow.
The workflow
The core flow is:
Upload → Process → Manage → Deliver
Upload
Assets can be added through the web application, API, CLI, CI/CD workflows, or the desktop application.
Process
Images can be optimized automatically and converted into formats such as WebP and AVIF. Different size variants can also be generated during processing.
Manage
Assets can be organized inside projects and managed using versions and tags.
This makes it possible to use stable references such as a published version or an environment-specific tag without manually replacing every asset URL.
Selected assets can also be protected instead of being publicly accessible.
Deliver
Published files can be delivered through stable URLs and used across websites, mobile applications, WordPress, headless CMS platforms, or other systems.
The main idea is:
Publish assets once. Use them everywhere.
Who is it for?
Smooth Bundle is primarily designed for:
solo developers,
small frontend teams,
small agencies,
developers managing multiple websites or applications,
WordPress and headless CMS users,
and teams that need a simpler alternative to combining storage, optimization, versioning, and delivery services.
It is not intended to be just another CDN or generic cloud storage product.
The goal is to provide a practical publishing layer for digital assets.
Current stage
Smooth Bundle is still at an early stage.
The product is functional, but I’m currently improving the onboarding, integrations, positioning, and overall developer experience.
I’m especially interested in feedback from developers who currently manage assets using several disconnected services or internal scripts.
You can take a look here:
How do you currently manage uploads, image optimization, asset versions, and delivery in your projects?
Top comments (0)