Jets is a deployment service that enables you to deploy to Serverless AWS Lambda.

It packages your existing Rails, Sinatra, or Ruby application and deploys it using AWS Lambda on your own AWS account, simplifying the deployment process.

Here are some Jets features:

• Rails Support: Deploying your existing Rails application to Serverless Lambda.
• Sinatra, Hanami, Rack: Essentially any Rack application can be deployed.
• CloudFront CDN: Jets can automatically create CloudFront Distribution for your Lambda Functions, Assets Serving, and File Uploads. Assets are precompiled and uploaded as part of the deploy process.
• Docker Support: Builds and pushes a Docker Image to ECR for deployment.
• Release History: Track your release history with the web browser or the jets release:history CLI command.
• Rollback Ability: Revert your app if needed with jets rollback to a previous version.
• ActiveJob Support: Jets supports a jets_jobs ActiveJob adapter that takes your Rails Job code and deploys it to Serverless. Sidekiq jobs and scheduler are converted to Serverless resources.
• CI: Continous Integration is baked in and supported. Jets can build a CodeBuild project dedicated to CI. It deploys on git push and can also deploy on a scheduled basis.
• WAF Protection: Jets supports Web Application Firewall to provide additional protection. A Jets Blanket Rate Limiter WAF Rule provides fundamental protection against DDOS attacks.

Yes. The Jets Service is required to use Jets. You can sign up for an account at www.rubyonjets.com. You can create an API Token Key to use Jets then.

Yes. There is a free usage period for first-time users. It starts once you start using Jets and lasts for two weeks. During the free usage period, you get unlimited stacks. Free usage is for new users and for that AWS account only. After the free usage period ends, a paid plan is required.

You get charged a flat-rate monthly price for each stack that Jets deploys and manages. Jets deploys to your AWS account.

You still pay for your AWS bill. Since you pay AWS directly, it can be much more cost-efficient than other SAAS platforms that charge a corresponding premium as you scale.

You can scale up your application as much as you want and are still only charged for that flat-rate monthly price for that stack. Other SAAS providers typically charge more as you scale. This can save money compared to other hosting solutions.

The AWS Lambda free tier gives you 1 million free requests and 400,000 GB-seconds of monthly compute time. It can handle a significant amount of traffic and processing power.

A stack is a unique deployment for your app. This includes project name, env, region, and AWS account. It can be thought of as a parent CloudFormation stack.

For clarity, your app's dev and prod deployment are two different stacks. Here's an example of 2 stacks:

• demo-dev
• demo-prod

If you deploy to multiple regions, those are also 2 distinct stacks.

Of course. Jets deploys your app to AWS Lambda, which is highly available inherently. AWS manages the servers, provides fault tolerance, and maintains them. That's what serverless is all about.

You can download receipts at any time:

1. Log onto to www.rubyonjets.com
2. Click on the Plan link in the top main menu
3. Click "Billing Portal"
4. At the bottom of this page, there's a "Billing History"
5. Click on the link with the invoice you want
6. Click "Download receipt"

100%. We dogfood our software. The Jets Service is built with Jets. This very page that you are viewing is served by a Rails app that was deployed with Jets. It's meta! Both the Jets Service web frontend and API backend components are built with Ruby on Jets. Jets Services are all highly available and scalable thanks to AWS Lambda.

Interestingly, you can use any Ruby version because Jets builds a Docker image with the Ruby version that your app uses. Generally, we'll follow and support the official Ruby versions that are not EOL.

You delete stacks with jets delete. The Jets Service stack record will be deleted as part of that process.

The projects are automatically removed from the dashboard when zero stacks are left. So you use the jets delete CLI command.

If you are on one of the legacy Jets plans, it will continue to work the same way it did before for now. The newer plans provide some legacy limits for older Jets projects for the time being.

• Hobby: 60 gem downloads/day
• Developer: Do not work with older Jets versions. Jets 6 is required.
• Team: Do not work with older Jets versions. Jets 6 is required.

Ultimately, support for Jets 5 and below will be discontinued. The focus will be on Jets 6 going forward.

If you are on one of the older plans, you are grandfathered into those prices. You'll lose your grandfather plans upon upgrading from a legacy plan. This includes if you let your credit card expire and you get downgraded. Be sure to keep your credit card info up-to-date. You can check out the old Jets 5 FAQ here