Solid and Scalable. Today and in the future.

Our structure is built like a true spine: Strong to support a wide range of capabilities, but is very flexible. Whether you’re a toddler in the media world or a full-grown international broadcast giant, Vidispine will adapt to your size and growth. But even more important, the architecture is presently utilizing current software and industry accepted standards but is designed to handle what ever the future holds.

From ground up, Vidispine is designed as enterprise software utilizing already well established industry software for databases, application servers, etc. The architecture is built with components that easily scale to hosted environments and clouds environments. Furthermore, Vidispine is agnostic to everything from OS to search engines, and can even operate in mixed environments The idea behind Vidispine is to always use 'best of breed' technologies. That means that we embrace already well established, but never adhere just to current standards. This philosophy has resulted in a product that is easy to deploy on a number of operating systems and application servers. It also means that you can handle millions of terabytes in different formats scattered over multiple systems and locations. And with “handle” we’re not only mean storing, but also editing and distributing the media.

Technology making it possible.

In Vidispine, storage devices, transcoders, network connections and network accelerators, are all treated as resources. Each Vidispine instance supports an unlimited amount of resources, and optimizes the use of each resource at every given moment. This means that the Vidispine instance can grow with the demands. Starting from a single server (or desktop) set-up with a single storage partition. At the other hand, it is easy to configure a very large system with storage policies, network optimization, cloud support, and even multi-site configuration.” Since Vidispine is all about the API, it is possible to do exhaustive machine testing on the entire Vidispine system. In Vidispine’s release process, this is done for all API calls, and also for a huge number of the supported configuration combinations. All in order to get the product that “just works”.