pastesite.com New paste

About pastesite.com

Company · updated October 2026 · 2 min read

pastesite.com is a small utility for moving text between people. You paste something, you get a link, the other person reads it. That is the whole product, and most of the decisions here are about keeping it that way.

Principles

How it is built

The front end is a React single-page app served as static files. The API is a Netlify Function that talks to Turso, a SQLite-compatible database, so a paste read is a single indexed lookup. Accounts and email confirmation are handled by Supabase Auth, and human verification on paste creation and abuse reports uses Cloudflare Turnstile.

LayerWhat it does
Static front endReact and Vite, lazy-loaded routes, no client-side database access
API functionAuthentication, rate limits, validation, and every database write
TursoPastes, folders, revisions, profiles, API key hashes, rate-limit events
Supabase AuthAccounts, sessions and confirmation emails
NetlifyHosting, CDN and the serverless runtime
Cloudflare TurnstileAbuse protection without a puzzle for most visitors

What we deliberately do not do

There is no full-text search across everyone's pastes, no public paste archive for crawlers, no analytics resale and no third-party advertising. Paste pages are excluded from search engines, and unlisted or password-protected pastes never appear in the public feeds.

We also do not claim that a paste is private in a cryptographic sense. Traffic is encrypted with HTTPS and passwords are hashed, but the content is readable by the service. For anything that is truly sensitive, use a password manager or an end-to-end encrypted tool.

Who runs it

pastesite.com is independently run and funded by its operator. There is no venture funding, no growth team and no plan to monetise the paste itself. Questions, bug reports and abuse reports all go through the contact page.

See what the site stores and why in the privacy policy. Create a paste

Frequently asked questions

Who owns pastesite.com?

It is an independently run site, funded by its operator and supported by the people who use it. There is no advertising or paid tier.

Is the site open source?

The code lives in a public GitHub repository, but the running service — database, keys and infrastructure — is operated privately. The API documentation describes the public surface.

How is the site paid for?

Static hosting, a small serverless function and a text database are cheap at this scale. The narrow feature set is what keeps it that way.