We’re opening early access to Tamery!
Visit the website and sign in, we'll be sending out lots of invites.
After so many months of work, we can’t wait to have you join us and hear your feedback!
Postgres, MySQL, MSSQL, ClickHouse and SQLite.
We went crazy after the attack on Railway.
For several weeks now, we've been checking every possible way user data could leak.
Fortunately, we haven't found anything, but we'll keep looking anyway and will most likely create a new service that searches for new vulnerabilities every week.
We have a very important area - your databases. That's why the security of your data comes first for us.
Our early access has ended, and now everyone can use Tamery!
It's still not a full release, we're still a couple of features away from that, but this is almost the final step.
We’re opening early access to Tamery!
Visit the website and sign in, we'll be sending out lots of invites.
After so many months of work, we can’t wait to have you join us and hear your feedback!
Postgres, MySQL, MSSQL, ClickHouse and SQLite.
don't let a hacker (or your agent) delete your database.
I just set up #2, wish i had done that sooner.
1. platforms like Supabase have backup features that allow you to restore to any MINUTE in the last 7 days.
..but if someone deletes your project, supabase deletes those backups with it. which is why #2 matters
2. AWS lets you set up a locked copy that you couldn't delete if you tried (seriously it won't even let the root account delete it until the 30 day lock runs out)..
mine is set up so that every night my agent backs up the whole database, encrypts it, and drops it into an s3 bucket with object lock on (compliance mode, 30 days)..
3. set up a "key watch" to look for irregularities in how your database is being accessed such as..
your supabase admin key (the one that can read and change every row) being used from an IP that isn't yours
someone logging into the database directly from a new IP, or as a database user you don't recognize
4. use scoped keys for your agents..
the old supabase access tokens have full access to every org and every project on your account.. including deleting them.
supabase now lets you make scoped tokens (only the projects and permissions that agent actually needs)..
5. obvious one - turn on RLS on every table... without RLS anyone who opens dev tools can delete your rows.
6. never give your agent your main DATABASE_URL.. give it its own read only login so it can't change or delete anything, even by accident
instead use github.. every schema change to the database is a migration file in a PR. CI checks it, it runs on staging first when it merges, then applies to prod when the deploy goes out
(make sure you have a CI check on any migration that fails on "DROP TABLE, DROP COLUMN, TRUNCATE, or a DELETE with no WHERE"... until a human signs off on it)
what else would you add?
Live data in oRPC is just an async generator.
Yield events on the server and for-await them on the client, fully typed. Add the Retry plugin and a dropped connection resumes from the last event.
@kylemathews We're trying to keep it up-to-date. We've already moved all data to SQLite storage and updated all live queries, but of course we may have missed something.
Oracle sounds cool, I think it could work well for our collection with oRPC and SSE https://t.co/LeZVFsv2l2
TanStack DB 1.0 RC1 is out!
Backend data that feels local: typed collections, live queries, and edits that show up instantly, then sync.
Start with your REST API. Add persistence, offline writes, and real-time sync later. Your queries stay the same.
We found an interesting description of Tamery. It says we work in the cloud, so it won't work for local development.
This AI came up with such a stupid reason 🤦
You only absolutely need internet to download the app and sign in. That's it.
All other actions don't require internet and will sync as soon as it becomes available.