{"_id":"5723eaebeae5090e00ee61f3","__v":53,"parentDoc":null,"user":"5723ea8efda3c70e005b88e3","project":"5723ead0fda3c70e005b88e5","version":{"_id":"5723eaebeae5090e00ee61f1","__v":3,"project":"5723ead0fda3c70e005b88e5","createdAt":"2016-04-29T23:14:51.190Z","releaseDate":"2016-04-29T23:14:51.190Z","categories":["5723eaebeae5090e00ee61f2","5723f854110e570e00486c7a","572a28f6d10a200e00b1cb14"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"0.1.0","version":"0.1"},"category":{"_id":"5723eaebeae5090e00ee61f2","version":"5723eaebeae5090e00ee61f1","project":"5723ead0fda3c70e005b88e5","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-04-29T23:14:24.983Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-04-29T23:14:25.012Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Welcome to Lever OS docs page!\n\nLever OS is the open-source cloud platform that allows fast-moving teams to build and deploy microservice-oriented backends in the blink of an eye. It abstracts away complicated infrastructure and leaves developers with very simple, but powerful building blocks that handle scale transparently.\n\n# How does it work?\n\nWith Lever OS, you don't think about servers. You think about services. Lever takes care of distributing your code on multiple servers and bringing up as many instances as necessary, depending on real-time demand. It routes and load-balances traffic transparently so you don't need to configure complicated reverse proxies or service discovery. It's all built-in.\n\nThe services are made out of a few exported functions that you develop and then deploy onto Lever. In JavaScript, for example, you export the functions as part of a `.js` file and then point Lever to that file. The functions become the API of your service and you can trigger them using an HTTP API, a Lever client library (Node and Go supported for now), or even the `lever` command-line tool.\n\n# Get started\n\nIf you are new, check out the [Quick Start](doc:quick-start) page to get up and running in a jiffy! When you are done with that, you might want to check the [Concepts](doc:basic-concepts) page and the [FAQ](doc:faq), to understand better how it all works.\n\n# Code\n\nLever OS is open-source. Head over to [the GitHub page](https://github.com/leveros/leveros) and give us a star!\n\n### Bugs\n\nPlease report bugs via [GitHub issues](https://github.com/leveros/leveros/issues).\n\n### Security Disclosure\n\nSecurity is very important to us. If you have any issue regarding security, please disclose the information responsibly by sending an email to `security [at] leveros.com` and not by creating a GitHub issue.\n\n# Getting Help\n\nIf you have a question, feel free to [open a GitHub issue](https://github.com/leveros/leveros/issues) or find us on [Gitter](https://gitter.im/leveros/leveros).\n\n# Status\n\nLever OS is in **beta**.\n\nThe following features of Lever OS are **experimental**:\n\n* Resources.\n* Streaming over the HTTP API.\n* Long-running methods (>10s). This includes streaming methods that keep the connection open for a long time.\n\nAreas we are focusing on next are:\n\n* Better logging support. For now, your log messages will show up in Lever OS's stdout, with prefix `lever://<env>/<service>`.\n* A browser JavaScript library, with batteries included.\n* Custom Docker images.\n* Rolling upgrades.\n* Configuration management, via extra custom fields in `lever.json`.\n* Support for Python.\n* Support for Java.","excerpt":"Serverless + Microservices = ♥","slug":"home","type":"basic","title":"Docs Home"}

Docs Home

Serverless + Microservices = ♥

Welcome to Lever OS docs page! Lever OS is the open-source cloud platform that allows fast-moving teams to build and deploy microservice-oriented backends in the blink of an eye. It abstracts away complicated infrastructure and leaves developers with very simple, but powerful building blocks that handle scale transparently. # How does it work? With Lever OS, you don't think about servers. You think about services. Lever takes care of distributing your code on multiple servers and bringing up as many instances as necessary, depending on real-time demand. It routes and load-balances traffic transparently so you don't need to configure complicated reverse proxies or service discovery. It's all built-in. The services are made out of a few exported functions that you develop and then deploy onto Lever. In JavaScript, for example, you export the functions as part of a `.js` file and then point Lever to that file. The functions become the API of your service and you can trigger them using an HTTP API, a Lever client library (Node and Go supported for now), or even the `lever` command-line tool. # Get started If you are new, check out the [Quick Start](doc:quick-start) page to get up and running in a jiffy! When you are done with that, you might want to check the [Concepts](doc:basic-concepts) page and the [FAQ](doc:faq), to understand better how it all works. # Code Lever OS is open-source. Head over to [the GitHub page](https://github.com/leveros/leveros) and give us a star! ### Bugs Please report bugs via [GitHub issues](https://github.com/leveros/leveros/issues). ### Security Disclosure Security is very important to us. If you have any issue regarding security, please disclose the information responsibly by sending an email to `security [at] leveros.com` and not by creating a GitHub issue. # Getting Help If you have a question, feel free to [open a GitHub issue](https://github.com/leveros/leveros/issues) or find us on [Gitter](https://gitter.im/leveros/leveros). # Status Lever OS is in **beta**. The following features of Lever OS are **experimental**: * Resources. * Streaming over the HTTP API. * Long-running methods (>10s). This includes streaming methods that keep the connection open for a long time. Areas we are focusing on next are: * Better logging support. For now, your log messages will show up in Lever OS's stdout, with prefix `lever://<env>/<service>`. * A browser JavaScript library, with batteries included. * Custom Docker images. * Rolling upgrades. * Configuration management, via extra custom fields in `lever.json`. * Support for Python. * Support for Java.