TL;DR - go to AssetCurrent and check it out.
Personal Story
While working on my hobby project with Babylon.js, I had to deal with digital assets such as SFX, textures, 3D models, etc.
Most of them I decided to craft myself or at least alter some FOSS assets found on the internet.
I didn’t have that many in-game entities that required digital artifacts, but the folder structure complexity exploded after just a couple of weeks.
In fact, crafting digital assets leaves a massive imprint in terms of the number of files and references to online resources, even if, by the end of the day, you only need 5-6 files for your project.
At a minimum, you need to keep track of:
- Input/source files (AKA references), which could also include online links.
- Work-in-progress files (usually project files from studio software like Blender, Audacity, etc.).
- A set of output files, which may include exports in different formats or slightly altered versions of the same asset. Even if you only need one final file, you’ll likely produce several collateral files during the creative process.
And that’s just for one asset.
As your collection grows, you’ll find that some entities may reuse existing artifacts, while others require full alternative versions for specific occasions (e.g., a branded version for a particular client app).
The real chaos begins when you create complex, multi-asset entities that require digital artifacts of different physical natures.
Imagine an NPC needing a 3D model, textures, sounds, UI icons, and even text dialogs.
To keep your “workshop” organized, you need a proper folder structure and naming convention.
However, you’ll constantly have to update and refine it as your production scales.
If you work with a team, you’ll also need separate documentation to explain what is where and likely use project management tools to track the progress of digital asset creation.
But the biggest challenge is ensuring that every collaborator stays on the same page with the latest updates and conventions. This:
a) Takes additional time and effort.
b) Introduces a risk of miscommunication, which can lead to business risks.
Naturally, we want to bring order to digital asset management. But how?
I reached out to professional communities and asked around. I spoke not only with software engineers but also with marketers, content creators, and productivity experts.
Interestingly, while many mentioned the existence of DAM systems, not many actually use them.
Instead, many companies end up developing their own in-house tools (often MySQL-based) to solve the aforementioned problems.
Curious about why this was the case, I checked out some popular DAM solutions and found my answers.
Beyond the obvious disadvantages (like high pricing and the lack of public demos), they don’t truly address the problem. Most DAMs are still folder-based, inheriting the same organizational pitfalls.
By the end of the day, they are more like repositories for final artifacts rather than creative workflow tools. This is why DAM systems tend to focus heavily on search capabilities, metadata, and file-proofing, rather than the creative process itself.
To solve the problem I mentioned in the beginning, I realized we need to change how we perceive digital assets.
They are not just static files - they are journeys from A to B. Therefore, an ideal DAM system for creative workflows should look more like project management software rather than a knowledge base.
Of course, I’m not the only person on the planet to think this way. Similar solutions do exist. However, there is still room for a competitive solution, especially in terms of price and public accessibility.
This is how the AssetCurrent was born.
AssetCurrent is currently in MVP stage, and I’m looking for feedback from different communities to better understand their needs and refine the target audience.
In terms of scale, I’m aiming at small to medium teams and individuals, which is why I offer a generous, risk-free 30-day free trial available to everyone.
(Absolutely don’t mind if big corps use it too :))
Below I provide competitive analysis of the existing solutions, and their pros and cons compared to AssetCurrent.
Competetive analysis
Classic DAM systems
Built for large-scale corporate needs (e.g., marketing departments, product catalogs).
They are still folder-based, meaning they inherit similar issues and don’t relieve you from documentation/communication overhead much.
Better suited for static or slow-growing repositories rather than creative workflows.
They often don’t provide public demos, so you have to book a demo.
Extremely expensive, costing hundreds of dollars per month for relatively small user/project packages.
Indirect competitors
Project management software
Notion is a popular example. It’s a powerful project management tool, and in theory can be adapted for DAM. However, It’s too broad and overwhelming on first use, requiring time to figure out how to set it up for DAM purposes which assumes a lot of files floating around.
VCS
Like GitLab/GitHub. Flexible tools with project management and collaboration capabilities. You can build very precise DAM creative workflows that integrates into your other engineering needs.
But achieving this requires expertise. Just dumping artifacts into repository doesn’t give you much benefits compared to cloud drive.
There is definitely a learning curve and such solutions are not suitable for non-technical users. You might be a software company, but your marketing and art teams are probably not.
Direct competitors
Filestage is probably the closest solution to what AssetCurrent offers. However FileStage still relies on folder structure, more expensive for small teams and supports fewer file formats for previewing.
In addition to images, PDFs, and MS Office documents, AssetCurrent previews videos, audio, some 3D formats, and syntax highlights text files in known formats.
Alright, what it all has to do with BabylonJS? Why it’s here?
As I mentioned, my BabylonJS hobby project directly inspired me to create AssetCurrent.
It also uses BabylonJS viewer to preview 3D files.
What does AssetCurrent offer?
- Smooth transition: you can attach artifacts as file uploads, links and raw text inputs. You don’t need to break existing processes and can transition at your own pace.
- Previews for uploaded files: images, PDFs, MS office files, videos, audio, text (with syntax highlighting where applicable), 3D models.
- Friendly structure for creative workflows.
- Easy collaboration and onboarding: Share and manage assets with your team instantly, keeping everyone aligned with minimal setup.
- Short but comprehensive documentation: Get started quickly with concise, easy-to-follow guides - no steep learning curve.
Landing page and short manuals will give more context on how AssetCurrent works.
AssetCurrent - landing page
5-minute manual - short manual
Structures Guide - examples of project structures
Rights Guide - project user rights guide
About Us - mostly about me 
