Pick a plan to empower your developers with automated database analysis
Free
$0 per month
For hobby projects and evaluation
All our standard features
Small selection of our rules
Pro
From $25 per month
For professional developers and teams
All our standard features
All of our rules
Increases security, performance and maintainability
Configurable for established projects
Custom
Contact us
Custom rules, self-hosting, whatever you need: we're here
All our standard features
All our rules, plus your own
Increases security, performance and maintainability
We'll help you configure your projects
VoIP support available
Self-hosting available
pgRITA Standard Features
Organization Management
No need to share passwords, all of your organization members can access pgRITA's features.
Continuous Integration
Trigger pgRITA from GitHub Actions, CircleCI, Travis or any other CI provider and ensure your changes pass our checks.
Tailored fixes
We don't just tell you what's wrong, many of our rules can suggest SQL that may solve the issue.
Rapid results
Results are usually ready to view within 5 seconds. During busy periods, paid accounts may be prioritized.
Unlimited tests*
Run a test every time you modify your database in development and on every CI run, we do not meter the number of runs.
Private reports
Reports are only visible to members of your organization.
* Reasonable usage policy applies to ensure system stability.
pgRITA Rules
Our rules cover a wide range of topics and can help database beginners and experts alike to ensure consistency and quality in their database schemas. Our rules help with:
- ensuring correct usage of primary and foreign keys
- ensuring consistency through the correct usage of constraints
- adding indexes in the appropriate places
- catching mistakes when defining database functions
- ensuring safe usage of
SECURITY DEFINERfunctions - correctly defining row level security policies
- ensuring consistent use of
GRANT - ensuring consistency in roles and entity ownership
- improving maintainability of functions, triggers, policies and other entities
- correct use of PostgreSQL types
- optimizing schema layout
- avoiding features during development that may be challenging to deploy (such as features requiring superuser privileges)
... and we're adding more in the coming months. If there's rules you'd like to see, please get in touch ─ maybe it's already in the works!