Build your next
in a fraction of the time
A secure and extensible user account system with sign up, authentication, email confirmation, password reset, and social login built in.
Kickstart your AI product with demo applications built on top of ChatGPT and DALL-E 2.
Choice of Front End
Built in REST APIs, API documentation, and client libraries for all your application's data.
Work with your database models directly in a browser with Django's built-in Admin UI.
Troubleshoot users' problems faster by experiencing the app exactly how they do.
Let users protect their accounts with an extra layer of security using Google Authenticator or similar.
Built-in tools to deploy to multiple cloud platforms in just a few clicks.
Get up and running in a single command using cross-platform Docker containers.
Fully-integrated demo of dynamic charts based on real data from your application.
Send email with any popular email service provider (ESP), including built-in, mobile-friendly templates for common emails.
Track errors in your production application in real-time with Sentry—the gold-standard for Django application monitoring.
Built on the secure Django web framework with sensible defaults to help avoid common security mistakes.
The ability to get a product to market quickly and testing the service are hallmarks in this landscape. SaaS Pegasus makes it possible not just to build your demo, but to get product-ready in weeks not months. That is what SaaS Pegasus helped us do at Savvy Education Inc. We were able to go from 0 to 1 in 3 weeks, building on top of Pegasus.
Get support from Pegasus's creator and hundreds of other developers building with Pegasus in our private Slack community.
Our documentation helps you get started with development, deployment, using best practices, and solving common problems.
Good question! Pegasus is a Django-backed SaaS boilerplate that puts you in control.You choose the technologies and features you want included, and Pegasus generates a unique codebase for your project. Instead of starting with Django's default skeleton project, you start with a bunch of extra work done for you—and nothing you don't need.
In short, Pegasus is for developers who want to jump start their projects.
Pegasus works well for experienced coders, data scientists looking to get into web development, and technical entrepreneurs looking to build their own MVPs.
Beginners and experienced developers alike will feel at home in Pegasus's mature—and always improving—codebase.
For a longer treatment of this question, see "Is Pegasus right for me?"
Yes, but it's a bit of work.
Pegasus is primarily for new projects and is not designed to integrate into existing codebases. Pegasus customers with existing apps typically either copy their app's code into a new Pegasus project, or copy the Pegasus features they need into their existing codebase. Both of these approaches work fine, but involve some copy/pasting.
We don't want you to be disappointed! If Pegasus isn't what you expected you can email us within 7 days for a full refund—no questions asked.
Well, we might ask you why you didn't like it so we can make it better in the future, but you don't have to answer and you'll still get your money back right away.
Pegasus lets you build multi-tenant applications—that is, applications that serve multiple customers (tenants) on top of a single platform. Each tenant (in Pegasus, a team) gets a siloed view of just their data.
Under the hood, Pegasus uses a single database and manages data isolation using foreign keys and a set of built-in helper functions in the application layer. You can read more about these tools in the teams documentation.
The main advantage of this architecture is that it is much faster to build and deploy on. And—if you follow the built-in patterns—it can scale to an almost-arbitrary size. We believe strongly that this makes it the best tenant architecture for most use cases.
That said, the single-database architecture may not be suitable for applications with extremely rigid security requirements. For those applications, a more siloed approach using something like django-tenants—which enforces data isolation at the database level—may be more appropriate. Using these alternate architectures will substantially increase the complexity of building and deploying your application.
It is possible, but a lot of work (and not supported), to adapt Pegasus to use a different tenant architecture. Very few Pegasus customers have ever needed to do this, even at scale.
Send us an email and we'll get back to you as quickly as possible!