When we saw Crunchydata’s post on HackerNews about Postgres running in a browser, we were inspired to replicate the feat and open-source the work to make it available to everyone. In this post, we briefly describe how we collaborated with Supabase to make it happen.

When it comes to securing the sensitive data in your database, we tend to err on the side of caution, which is why we're implementing encryption for Snaplet snapshots.

How do you like your data scrambled? Soft? More on the firm side? How about exactly the same as the source data? It's now possible with Snaplet Copycat!

There's never been a better time to get your data into shape! Whether you're working on an established project with a big ol' database, or starting something new, Snaplet makes it super easy for you to get production-accurate data you can actually code against in your development environment.

Snappy and the rest of the Snaplet team are just thrilled to be part of the Netlify Jamstack Innovation Fund!

Imagine the ability to “live-reload” the data in your database. Imagine being able to add data to your database from within your CLI with a simple command, and immediately code against it. Snaplet Proxy allows validation of transformations on the fly. This means you can stay in your editor and hence, stay in the flow.

Coding without access to production-realistic data sucks. Today, we’re making Snaplet easier to use, and more powerful than ever before, with Javascript Transformations and Proxy. Transform your PII, and see it happen live with Proxy - a whole new kind of magic with Snaplet.

How is Copycat different from our initial faker library? The libraries out there for generating fake data mostly generate sequences of data. What we were looking for is a mapping of values, instead of a sequence. This is why we decided to write Copycat.

Our founder Peter had the opportunity to demo Snaplet at the Redwood V1 launch last night. Here's a short round-up of what he had to share.

Have you ever used Snaplet to restore your entire production database to your local environment when you're actually only changing data in a few specific tables? With our new `snaplet restore --data-only --tables` flag, you can be more granular about what data you want refreshed, making it quicker and easier than ever before to Snappify your workflow!

Writing company documents and policies is no easy undertaking, but getting your engineering team to actually read them is a bit of a challenge. In this post, we share how we got our devs to literally consume our employee value proposition (EVP)

As a Supabase user, you may have struggled with setting up multiple environments on Supabase, and populating each of those with data. We've created a step-by-step guide to show you how Snaplet solves that for you.

We dive into the rabbit hole of coding against actual data and provide six reasons why you should be using Snaplet.

Last week, Snaplet cofounder, Scott Chacon, presented a talk on Prisma Day to demo what Snaplet looks like and how easy it is to use our database snapshot tool.

Snaplet makes it super easy to set up a mock version of your production database for testing environments. Here we'll give you a quick rundown of how our tool works.

Here at Snaplet, our staff ratio between the design and engineering team is 1:1. This means our designers are always looking for ways to save our developers' time and make their work easier. So when we were looking for platforms to build our marketing page in, we needed something that was quick, flexible and scalable. In the end we settled on Webflow. Here's why.

Here at Snaplet, life is all about PII. In fact, our whole team is obsessed with it. I'm not talking about the lobster pie that Snappy (head of naps and smiles) loves so much. What I'm referring to, is a whole different recipe, and if not handled with care, could leave a bad taste in your mouth. So what is PII then? Let's delve in.