VividEngine

Almost a full year after launching and running our web hosting CDN product we have seen first-hand how the capabilities of frontend developers are increasing at a rapid rate. New SaaS and PaaS products provide solutions for most basic product functions (like authentication via Auth0, payments via Stripe, and database via Fauna ) empowering that developers can rapidly bring their products to market by simply tieing these services together via simple APIs. This trend also encompasses low-code and serverless computing.

While many basic functions are already being addressed we have seen that frontend developers still struggle to deploy rich media (images, video, audio) at scale in a cost-effective manner.

The cheapest bare-bones solutions like AWS require a time-consuming setup process fraught with challenging technical configuration. Complete end-to-end media hosting solutions fall short of making integration simple and are extremely cost-prohibitive for startups or even popular projects that are lightly monetized.

It may seem hard to believe, but there really is no cost-effective solution for simple and scaleable image, video, audio, and general file handling and global delivery. We believe we can provide a solution that's significantly better than existing options while also being 10 times cheaper.

We want to create a platform that is developer-focused instead of non-developer focused. We are following the model Stripe has set:

• Clear API
• High Quality Documentation
• User Interface that reflects the API offering comparable functionality in a simple UI.

Users, including developers, want to be abstracted from complexity. This is evident when a project integrates a 3rd party service (Intercom), utilizes an open-source project (React), or redirects externally for functionality (Paypal). This is the basic desire we want to build VividEngine upon.

Our overarching goal is to attract users looking for low cost (comparably) file infrastructure that attracts backend integrations, and web/app integrations using SDKs.