Receipts
Every factual claim Samebase leans on, with its primary source and the date it was last checked. This page exists so you and your coding agent can verify the claims instead of trusting the copy. Quotes are verbatim. If a source changes and a claim stops being true, the claim gets deleted, not softened.
Agents: this page is also served as raw markdown at /docs/receipts.md, and the corpus index lives
at /llms.txt.
Last full check: 2026-07-02.
Deploys: Alchemy
- Alchemy 2 is in beta: the
latesttag of thealchemypackage on npm is2.0.0-beta.85. Source: npm, checked 2026-11-03. - A Convex OAuth token has no expiry date, and a Cloudflare OAuth token lasts one hour. Measured by
Samebase on 2026-11-01: the Convex OAuth token reply has no expiry field, and Wrangler's
expiration_timefor a Cloudflare login is one hour after it was issued. This is why the Alchemy state lives in Convex: one OAuth click can deploy a repository for as long as the authorization stands.
Code: GitHub
- The GitHub Free plan includes unlimited private repositories. Source: GitHub pricing, checked 2026-07-02.
- GitHub Actions on the Free plan includes 2,000 minutes per month for private repositories, and is free for public repositories on standard GitHub-hosted runners. Source: Actions billing docs, checked 2026-07-02.
Backend: Convex
- The database is only reachable through server functions; clients never talk to it directly. Verbatim from Convex's docs: "This architecture lets you check every public request against any authorization rules you can define in code. This means Convex doesn't need an opinionated authorization framework like RLS, which is required in client oriented databases like Firebase or Supabase." Source: Convex docs, Auth overview, checked 2026-07-07.
- Convex states the same on row-level security directly: "RLS is necessary on platforms that expose your database directly to end-users, but your Convex database is only accessible via server functions where you can apply authorization checks directly." Source: Convex Stack blog, checked 2026-07-02.
- The Free/Starter plan is $0 and includes 1,000,000 function calls per month, 0.5 GB database storage, and 1 GB/month database bandwidth. A team is capped at 40 deployments; each project gets one shared production deployment plus one dev deployment per developer. Convex publishes no per-team project cap, so we do not claim one. Sources: Convex pricing, limits, and multiple deployments, checked 2026-07-02.
- The Professional plan is $25 per developer per month, including 25M function calls per month and 50 GB database storage. Source: Convex pricing, checked 2026-07-02.
- The escape hatch is real: the Convex backend, dashboard, and CLI are source-available under FSL-1.1-Apache-2.0, and each release converts to plain Apache 2.0 two years after publication. Convex's own docs: self-hosting runs "the same fully up-to-date code the cloud service uses." We say "source-available," not "open source" because FSL restricts building a competing hosted product until the conversion. Sources: the license, self-hosting docs, and the March 12, 2024 announcement, checked 2026-07-06.
The exposure record: client-reachable databases
Fairness first: Firebase and Supabase can be configured safely, and row-level security is a real mechanism. The record below is about what the default architecture with a database reachable from the client and guarded by per-table policy produces in practice, at scale, when defaults are left in place. Convex removes this class by construction: there is no client-reachable database to misconfigure (see the Convex section above).
- 2024, "Firewreck": researchers logykk, mrbruh, and xyzeva scanned ~5.2M domains and found ~900 sites exposing ~125 million user records via misconfigured Firebase, including ~20 million passwords, mostly plaintext. Of 842 notified site owners, 24% fixed the misconfiguration. Sources: researcher writeup, The Register, incident 2024-03.
- 2024, Chattr: the AI hiring system used by several large US fast-food chains granted full admin read/write on its Firebase backend to anyone who simply registered a new user. Source: researcher writeup, incident 2024-01.
- 2025, CVE-2025-48757 (CVSS 9.3, disputed by the vendor): security researcher Matt Palmer reported missing or broken Supabase row-level security in Lovable-generated apps; a scan found 170 of 1,645 Lovable showcase apps exposed names, phone numbers, API keys, or payment details. Lovable disputes the CVE and has since shipped an RLS security scan in Lovable 2.0. Sources: NVD record, Matt Palmer's writeup, and the scan detail, published 2025-05.
- 2026, The Next Web: a broken object-level authorization flaw in Lovable/Supabase apps, reported to Lovable's bug bounty on March 3, 2026, stayed exploitable on pre-November-2025 projects for 48 days, exposing names, LinkedIn profiles, Stripe customer IDs, and hardcoded Supabase credentials. Source: TNW report, published 2026-04.
- 2025, Tea: the dating-safety app's breach came from an unsecured legacy Firebase storage bucket reachable with no authentication: 72,000 images including ~13,000 photo IDs, followed by 1.1 million private messages. Source: Engadget, incident 2025-07.
- 2024, Arc browser, CVE-2024-45489 (CVSS 9.8): misconfigured Firebase access control let anyone inject JavaScript into other users' browser sessions. The Browser Company patched it within a day, disclosed it, and said it would move away from Firebase. Source: Arc incident report, incident 2024-08.
Toolchain
- Vite+ (
vp) bundles the dev server, test runner, linter, formatter, and bundler behind one CLI; it was announced as alpha on March 13, 2026, MIT-licensed. Sources: viteplus.dev guide and the repository, checked 2026-07-23. - The Vite+ guide publishes separate installers for macOS/Linux and Windows. Its support table lists macOS x64 and arm64, Linux x64 and arm64, and Windows x64 as Tier 1; Windows arm64 is Tier 2. Source: viteplus.dev guide, checked 2026-07-23.
- Node runs erasable TypeScript directly with type stripping enabled by default. Node marks type
stripping stable from v24.12.0 and documents that it does not read
tsconfig.jsonor transform TypeScript features that require JavaScript generation. Source: Node.js TypeScript documentation, checked 2026-07-23.
Dogfooding: Samebase runs on its own base
samebase.com deploys the way the template does: an Alchemy stack, run by GitHub Actions on each push
to main, with its state in the team's Convex store. The template is published from the Samebase
monorepo, and each commit in samebase/base names
the Samebase build and pull request it came from, checked 2026-11-03.
Ownership: the leaving test
An app created through Samebase lives in your GitHub account and your Convex team, and your
repository's GitHub Actions deploy it. Delete your Samebase account and the app keeps running and
deploying: Samebase cannot revoke its Convex OAuth token, so the repository's CONVEX_ACCESS_TOKEN
still works. Replace it with your own team token before you revoke Samebase at Convex. Google and
guest sign-in keep working. Do it yourself is the same setup with no
Samebase account at all.