Leostream

Leostream, founded in 2002, is a privately held technology company based in Waltham, Massachusetts. Its flagship product is a connection broker for virtual desktop infrastructure (VDI) and resources hosted in the datacenter.

Leostream
Private
IndustryTechnology;
Founded2002
FounderDavid Crosbie
HeadquartersWaltham, Massachusetts
ServicesVirtual Desktop Connection Broker
Websitewww.leostream.com

Software

Leostream develops a vendor-neutral connection broker, which is software that maps end users to computing resources, such as desktops, that are hosted in a data center. A connection broker integrates end-user access points, including thin clients, laptops and Web browsers, with back-end systems hosting desktops and applications. It also integrates all other data center systems required for a virtual desktop infrastructure, including security, authentication, and load balancing systems.[1]

The Leostream Connection Broker provides a single interface to manage a range of operating systems, physical and virtual desktops, and display protocols commonly found in enterprise environments. Delivered as a virtual appliance, the Leostream Connection Broker supports the major hypervisors, including those provided by VMware®, Citrix®, Red Hat®, and Microsoft®.[2][3] Leostream supports both Microsoft Windows and Linux operating systems in the datacenter.[4] In addition, the Leostream Connection Broker is optimized for OpenStack® powered clouds and is a partner in the HPE Helion OpenStack program and is SUSE OpenStack Certified.[5]

Once installed, the broker is used to add desktop and application resources, define authentication servers, build pools and plans, and configure client and end-user policies. For purely physical environments, the Leostream Connection Broker is packaged as an ISO that can be installed on certain hardware.[6]

Leostream supports over ten display protocols, including Teradici PCoIP, HP RGS, and OpenText Exceed onDemand, which are tailored for systems running graphic-intense applications. The Leostream Connection Broker is also used to deliver cloud/hybrid deployments and Desktop-as-a-Service (DaaS) with desktops hosted on AWS, Azure or OpenStack clouds.[7]

gollark: It's a good thing, though.
gollark: In this case, I want a thing I can access on my phone and stuff without installing any additional software on it, and which can benefit from browsers' really nice rendering engines.
gollark: Browsers provide a useful cross-platform environment which is well-sandboxed but still has decent access to a lot of stuff, which allows you to run an application in a few seconds without installing anything, and which can interact easily with some server somewhere.
gollark: The interweb™ is *good*.
gollark: It would take much longer to implement, be significantly less readable, run somewhat faster, and have more security issues.

References
  1. ChannelWeb, “Leostream Roars Into Desktop Virtualization”, 26 March 2009, "Archived copy". Archived from the original on 2009-07-01. Retrieved 2009-06-24.CS1 maint: archived copy as title (link)
  2. Brian Madden.com, “How Does Leostream Still Exist?”, 11 February 2009, http://www.brianmadden.com/blogs/brianmadden/archive/2009/02/11/how-does-leostream-still-exist.aspx/
  3. IT 2.0, "Virtual Infrastructure products: features comparison.", accessed 7 July 2009, http://www.it20.info/misc/virtualizationscomparison.htm
  4. InfoWorld, "Leostream connection broker technology still pushing forward" http://www.infoworld.com/article/2634693/virtualization/leostream-connection-broker-technology-still-pushing-forward.html
  5. The Virtualization Practice, "Leostream - One Broker to Rule them All", 26 June 2015, https://www.virtualizationpractice.com/leostream-one-broker-rule-33345/
  6. eWEEK, "Leostream Connects VDI", http://www.eweek.com/pc-hardware/REVIEW-Leostream-Connects-VDI-
  7. The Virtualization Practice, "Leostream - One Broker to Rule them All", 26 June 2015, https://www.virtualizationpractice.com/leostream-one-broker-rule-33345/
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.