github.com/hhsnopek/up@v0.1.1/Readme.md (about) 1  2 3 Up deploys infinitely scalable serverless apps, APIs, and static websites in seconds, abstracting away complex infrastructure so you can get back to writing code, all while providing cost effective, scalable, and global services. 4 5 Up currently supports Node.js, Golang, Python, Crystal, and static sites out of the box. Up currently targets AWS Lambda and API Gateway as its platform, however more will be available in the future, you can think of Up as a serverless provider-agnostic Heroku style experience. 6 7 Check out the [documentation](docs) or the [examples](https://github.com/apex/up-examples) to get started. 8 9  10 11 ## Features 12 13 Open source community edition: Coming soon. 14 15  16 17 ## Pro Features 18 19 Close sourced pro edition: Coming less soon. 20 21  22 23 ## Pricing 24 25 Updated as of July 2017 based on public information. Some services offer a restricted free version, or free access for solo developers – this table is based on commercial use. 26 27  28 29 ## FAQ 30 31 <details> 32 <summary>Is this a hosted service?</summary> 33 <p>There are currently no plans for a hosted version. Up lets you deploy applications to your own AWS account for isolation, security, and longevity, don't worry about a startup going out of business.</p> 34 </details> 35 36 <details> 37 <summary>Why isn't Up licensed MIT?</summary> 38 <p>Up is licensed in such a way that myself as an independent developer can continue to improve the product and provide support. Commercial customers receive access to a premium version of Up with additional features, priority support for bugfixes, and of course knowing that the project will stick around! Up saves your team countless hours maintaining infrastructure and custom tooling, so you can get back to what makes your company and products unique.</p> 39 </details> 40 41 <details> 42 <summary>How is this different than other serverless frameworks?</summary> 43 <p>Most of the AWS Lambda based tools are function-oriented, while Up abstracts this away entirely. Up does not use framework "shims", the servers that you run using Up are regular HTTP servers and require no code changes for Lambda compatibility.</p> 44 </details> 45 46 <details> 47 <summary>How much does it cost to run an application?</summary> 48 <p>AWS API Gateway provides 1 million free requests per month, so there's a good chance you won't have to pay anything at all. Beyond that view the <a href="https://aws.amazon.com/api-gateway/pricing/">AWS Pricing</a> for more information.</p> 49 </details> 50 51 <details> 52 <summary>Do I have to manage instances or container counts?</summary> 53 <p>Nope! Up scales to fit your traffic on-demand, you don't have to do anything beyond deploying your code.</p> 54 </details> 55 56 <details> 57 <summary>How much latency does Up's reverse proxy introduce?</summary> 58 <p>With a 512mb Lambda function Up introduces an average of around 500µs (microseconds) per request.</p> 59 </details> 60 61 <details> 62 <summary>Can I donate?</summary> 63 <p>Yes you can! Head over to the <a href="https://opencollective.com/apex">OpenCollective</a> page. Any donations are greatly appreciated and help me focus more on Up's implementation, documentation, and examples. If you're using the free OSS version for personal or commercial use please consider giving back.</p> 64 </details> 65 66 ## Community 67 68 - [Example applications](https://github.com/apex/up-examples) for Up 69 - [Slack](https://apex-dev.azurewebsites.net/) to chat with apex(1) and up(1) community members 70 - [Blog](https://blog.apex.sh/) to follow release posts, tips and tricks 71 72 <a href="https://apex.sh"><img src="http://tjholowaychuk.com:6000/svg/sponsor"></a>