Web frameworks
Ruby on Rails
Use Rails when you want those pieces in one Ruby project. Choose where it will run and who can read or change the saved records.
Compare tools for building and running a web app. See what each one does, what it costs, and what you’ll need to set up.
Showing 97–120 of 121 tools
Web frameworks
Use Rails when you want those pieces in one Ruby project. Choose where it will run and who can read or change the saved records.
CSS frameworks
Useful when an existing project already uses Sass and one change needs to reach several forms or screens.
Error monitoring
Useful when a visitor says something broke and you need more than a screenshot to understand why.
UI libraries
Useful when you want to start with a styled control and expect to change its appearance or behavior in your own code.
Design
Useful when you work on a Mac or have an existing Sketch file to keep editable. A team can review a shared design in a browser.
Payments
Use Stripe if you want a ready-made payment page and need to decide which accounts get paid features. Check whether you’ll sell in your own name or through Managed Payments.
Databases and backends
For an app that needs saved records, accounts and uploads together, with access rules you can test through ordinary accounts.
Web frameworks
Use Svelte when a screen needs to respond to a choice and you want the display and its behavior together in one component file.
Languages and runtimes
Use it when you have a specific device feature to build or an existing Swift project to maintain.
CSS frameworks
Useful when your app already uses Tailwind or you want to decide how the form looks one property at a time.
Forms and surveys
Use it for a waitlist where you want a custom ending, a simple embed or a shared password without paying per response within fair use.
Background jobs
For apps that need to run code for a report, import or other slow task outside the web server.
Transactional email
For an app that can connect a verified sender and wants to trace email delivery over time.
Forms and surveys
Use it when the order of questions and the ending matter to the experience, and you can budget for responses across all the forms in your account.
Languages and runtimes
Use it to understand the checks in an existing JavaScript or TypeScript project before changing how the app builds.
File storage and media
Use it when a feature needs an upload button, progress and a saved file record. If those files are confidential, confirm the paid private-file setup before taking customer uploads.
Uptime and status
Use it when the first question is whether a known address responds. If the address answers but a visitor cannot finish a booking, check the customer action separately.
App builders
A fit when you know how the page should look or feel, and want to turn it into an app you can inspect and keep as code.
Hosting
A fit to investigate when you want to review changes from a connected code project and are prepared to choose a plan, set up storage and check app permissions yourself.
Code editors
Consider it if an existing Windows or .NET project calls for Visual Studio and specific development tools. Check the project’s setup and your edition before installing.
Code editors
Start here if you have a project folder and want a file browser and change review. Choose separately whether to use Copilot or another extension.
Web frameworks
Use it when you need to turn browser code into files a host can serve. Plan separately for work a server must do, such as saving a shared booking.
Web frameworks
Use Vue when you want to improve part of an existing page first and keep the option to build a larger interface later.
Databases and backends
For an app whose team wants to arrange backend steps in an editor and connect its own customer screens.