linse+hannes: revise home
This commit is contained in:
parent
7d88385bc4
commit
9f978450a6
2 changed files with 24 additions and 35 deletions
2
About
2
About
|
@ -101,4 +101,4 @@ have somehow not been of particular interest to paying customers (yet).
|
|||
|
||||
## Contact
|
||||
|
||||
If you want to get in contact with us, write an email to us AT robur DOT io.
|
||||
If you want to get in contact with us, write an email to team@robur.io.
|
||||
|
|
57
Home
57
Home
|
@ -1,19 +1,8 @@
|
|||
---
|
||||
title: What is robur?
|
||||
---
|
||||
At robur, we build performant bespoke minimal operating systems for high-assurance services.
|
||||
With our approach to systems development we provide the following advantages for you:
|
||||
* systems based on the unikernel pioneer [MirageOS](https://mirage.io)
|
||||
* secure implementation guarded against memory corruption, typelevel problems, leaky abstraction and unforeseen state
|
||||
* ready for the cloud, services run on all major hypervisors
|
||||
* instant boot
|
||||
* competitive performance comparable to C
|
||||
* can target embedded devices because of small size and the ability to compile to native code
|
||||
* minimized state allows to reason about entire systems and their adherence to the specification
|
||||
* extensive library ecosystem, yet minimal trusted code base at runtime
|
||||
* rapid prototyping with a seamless path from prototype to production
|
||||
|
||||
Computers on the Internet get compromised mostly to gain or block access to data.
|
||||
Computers on the Internet get compromised mostly to gain or block access to data:
|
||||
User data is being downloaded, leaked and sold, or ransomware blocks access to user data until a fee
|
||||
is paid. Other common attacks target compute resources, to use them in denial of service
|
||||
attacks or to manipulate opinion with chatbots.
|
||||
|
@ -22,28 +11,28 @@ Common software stacks often include legacy parts at runtime that provide unnece
|
|||
Critical security updates are rarely deployed on time, because they result in unforeseen behaviour. Also, lots of embedded
|
||||
devices are missing a secure update channel.
|
||||
|
||||
[//]: # (====== marker fuer linse - aber ein comment in markdown)
|
||||
We at robur are building minimal services, called *unikernels*, from scratch with security in mind,
|
||||
instead of trying to fix decades-old software designed based on demands from earlier days.
|
||||
Each
|
||||
service is executed as a virtual machine on any major hypervisor, and contains only the
|
||||
strictly necessary code.
|
||||
The number of lines and the binary size of a unikernel with HTTP
|
||||
and TLS support is around 4% compared to a virtual machine using a conventional
|
||||
UNIX / Linux operating system.
|
||||
The security of a unikernel is improved by the reduction of the attack surface.
|
||||
At robur, we build performant bespoke minimal operating systems for high-assurance services.
|
||||
With our approach to systems development we provide the following advantages for you:
|
||||
* cutting-edge systems programming and security research
|
||||
* systems based on the unikernel pioneer [MirageOS](https://mirage.io)
|
||||
* secure implementation guarded against memory corruption, typelevel problems, leaky abstraction and unforeseen state
|
||||
* ready for the cloud, services run on all major hypervisors
|
||||
* instant boot (milliseconds)
|
||||
* competitive performance (TLS 85% the speed of OpenSSL) comparable to C
|
||||
* can target embedded devices, small size (~4% size of UNIX based system), compilation to native code
|
||||
* minimal codebase without mutable state allows to reason about entire systems and adherence to specification
|
||||
* extensive library ecosystem, yet minimal trusted code base at runtime
|
||||
* rapid prototyping with a seamless path from prototype to production
|
||||
* possibility to formally verify important parts with a therorem prover
|
||||
|
||||
Our unikernels are implemented in a functional programming language with a static
|
||||
type system and automated memory management.
|
||||
Buffer overflows and double frees are no concern to us.
|
||||
A unikernel avoids these common attack vectors by the choice of the programming language.
|
||||
|
||||
We can prototype rapidly, because the type system detects errors early, and we don't need to manage memory by hand.
|
||||
Turning a prototype into production is usually a question of fine-tuning its performance.
|
||||
Our team is eager to develop applications for high assurance, which seamlessly
|
||||
integrate in your existing infrastructure. Contact us and we'll collaboratively
|
||||
develop a more secure architecture and a smooth migration plan for your
|
||||
organization. And we'll implement and deploy this together at your organization.
|
||||
We bring a variety of solutions, including basic network services, DNS, DHCP,
|
||||
TLS, persistent storage (like git), and are happy to expand these to your needs.
|
||||
|
||||
Our declarative programming style makes it even possible to
|
||||
formally verify an entire virtual machine using a theorem
|
||||
prover.
|
||||
|
||||
The boot time of a unikernel can be measured in a few milliseconds, redeployment
|
||||
after updates is instantaneous. We can create unikernels on demand.
|
||||
Take a look at our [technology](/Technology), learn about our [concept and
|
||||
team](/About) or browse some [project](/Projects). You can reach us by mail at
|
||||
team@robur.io.
|
||||
|
|
Loading…
Reference in a new issue