Snaplet supercharges your development workflow by giving you production-like data that you're in control of
This is how:
Do I have access to data?
Yes
No
Do I have access to data?
Yes
No
snaplet.config.ts
Snapshot: {
Generate: {
Select, subset, transform and copy data into a snapshot
Select
Select or exclude data to copy.
Read more
Read more
Subset
Smaller snapshots are faster and less data is easier to work with. You can capture a defined subset of data in your snapshot.
Read more
Read more
Transform
Automatically transform sensitive values like names, email addresses and phone numbers to make your snapshot safe to share.
Read more
Read more
Snaplet automatically generates data based on your schema
Using Typescript, you tell us just the parts of your schema you want to see generated.
We'll use AI to generate data matching the types and names in your schema.
Any related data needed will be generated automatically.
Read more
We'll use AI to generate data matching the types and names in your schema.
Any related data needed will be generated automatically.
Read more
Snapshot: {
snaplet.config.ts
Seed: {
Select, subset, transform and copy data into a snapshot
Select
Select or exclude data to copy. Read more
Subset
Smaller snapshots are faster and less data is easier to work with. You can capture a defined subset of data in your snapshot. Read more
Transform
Automatically transform sensitive values like names, email addresses and phone numbers to make your snapshot safe to share. Read more
}
Snaplet seed automatically creates data based on your schema
Using Typescript, you tell us just the parts of your schema you want to see generated.
We'll use AI to seed data matching the types and names in your schema.
Any related data needed will be seeded automatically.
This is the quickest and easiest way to try out Snaplet! Read more
We'll use AI to seed data matching the types and names in your schema.
Any related data needed will be seeded automatically.
This is the quickest and easiest way to try out Snaplet! Read more
}
Now that you have production data you can restore it in your development environment via the Snaplet CLI
To install the CLI
npm install --dev snaplet
Local development environment
Restore to your local development database.
Test & preview environment
Get isolated deployment environments with unique, isolated databases for each preview deployment.
CI/CD
Automate your CI/CD development infra-structure requirements with Snaplet. Seed is perfect for end-to-end testing. Use GitHub Actions to automatically restore snapshots to your target environment.
Now that you have production data you can use a Snaplet Client to restore it in your development environment
CLI or VS Code
Local development environment
Restore to your local development database, or use Snaplet's VS Code extension for a managed developer database.
Test & preview environment
Get isolated deployment environments with unique, isolated databases for each preview deployment.
CI/CD
Automate your CI/CD development infra-structure requirements with Snaplet. Use GitHub Actions to automatically restore snapshots to your target environment.
CLI
To install the CLI
npm install --dev snaplet
– OR –
VS Code Extension
Not sure which flow is right for you?
Case 1: You have no data (e.g. very early stage startup)
You don’t have any data for it to be valuable to code against, use Seed.
Case 2: You have existing production data, but no access to it
You are interested in ways of getting better development data, but don't have or can't give Snaplet access to production, use Seed.
Case 3:You have existing production data, but it contains sensitive info
You are interested in ways of getting better dev data, but cannot /or do not want to risk exposing sensitive data, use Seed.
Case 4: Has existing production data, can access it, want to copy it
If it is more valuable to you to code against realistic data from your production database, and you're able to risk making use of production data, try Snapshot.
You don’t have any data for it to be valuable to code against, use Seed.
Case 2: You have existing production data, but no access to it
You are interested in ways of getting better development data, but don't have or can't give Snaplet access to production, use Seed.
Case 3:You have existing production data, but it contains sensitive info
You are interested in ways of getting better dev data, but cannot /or do not want to risk exposing sensitive data, use Seed.
Case 4: Has existing production data, can access it, want to copy it
If it is more valuable to you to code against realistic data from your production database, and you're able to risk making use of production data, try Snapshot.
