Commit database plans as code
Connect
SPIRITT
XataXata
Postgres planned right the first time
SPIRITT builds your app and plans its Xata database from live facts. It picks regions, Postgres images, extensions and instance types that fit your limits, writes the setup into your repo and audits organization access.
What you can do with Xata.
Architecture from real options
Check regions, Postgres images and extensions before committing to a design.
Sized within your limits
Compare instance types against project limits so plans fit before anyone provisions.
Organization kept tidy
Review organization status and API keys, and update organization details when they change.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your app. Describe users, data and compliance needs.
02
Connect Xata
Connect Xata, then GitHub so database plans become reviewed configuration.
03
Delegate the build
Describe the product. SPIRITT plans the database, writes the code and keeps the setup current.
Hand over a mission.
Choose a mission. Make it yours.
Put Xata to work.
Postgres planned right the first time
Questions
Xata, with SPIRITT.
01What can SPIRITT see in Xata?+
Your organization, project limits, deployable regions, Postgres images, extensions, instance types and API keys.
02Can it check Postgres extensions?+
Yes. It lists the extensions available for each Postgres image, so designs rely only on what exists.
03Does it help choose a region?+
Yes. It lists every region where branches can be deployed and matches them to your users and residency rules.
04Can it size instances?+
Yes. It compares instance types in a region against your project limits.
05Can it change organization settings?+
It updates organization details such as the name.
06Does SPIRITT build the app itself?+
Yes. SPIRITT writes the application and infrastructure code in your repositories, using Xata's live options for the database plan.