Ship database-backed app code
Connect
SPIRITT
PrismaPrisma
Build on your real database
SPIRITT connects Prisma projects, databases, schema, and SQL into working software and accountable database operations, from a new app backend to a tested recovery workflow.
What you can do with Prisma.
From project to working app
Provision a database, inspect its schema, and build an application using securely handled connection details.
Data changes with evidence
Run scoped queries and approved SQL changes, then verify the resulting records and structure.
Operations beyond a query
Monitor usage, review access, and validate restored databases without confusing a started operation with a finished one.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for Prisma Postgres apps and database operations.
02
Connect Prisma
Connect Prisma with access to the account and records your mission needs. Add the companion apps you want SPIRITT to work across.
03
Delegate an outcome
Describe the result, owners, and approval rules. SPIRITT builds and runs the workflow around your Prisma data.
Hand over a mission.
Choose a mission. Make it yours.
Put Prisma to work.
Turn the database into delivered software
Questions
Prisma, with SPIRITT.
01Is this Prisma ORM or Prisma Postgres?+
The connection operates Prisma platform resources and Prisma Postgres databases. It can also help build application code, but ORM code changes are separate engineering work rather than a platform action.
02Can SPIRITT run writes as well as reads?+
Yes. SELECT queries and SQL commands that modify data or schema are separate supported actions. SPIRITT uses the inspected schema, scoped approval, and parameterized queries for planned changes.
03How are connection secrets handled?+
New database and connection responses can include credentials. SPIRITT keeps them in protected secret storage and avoids placing them in chat, reports, or shared source files.
04Can it restore over production?+
The restore action creates a new database from a backup. SPIRITT monitors the new instance and validates it before any separately approved application cutover.
05Can it monitor consumption?+
Database usage provides storage and operation metrics for a selected period. SPIRITT can run a capacity dashboard and alerts without inventing latency or billing measurements that are not returned.
06What happens when a connection is deleted?+
Its database access is immediately revoked. SPIRITT checks dependent applications and verifies replacement access before an approved revocation; database and project deletion are even broader irreversible actions.