About Tonta

Where the name came from

“Tonta” means “silly” or “stupid” in Spanish. My daughter suggested it as a joke—then doubled down when I reminded her it wasn’t exactly flattering. The joke stuck, and now a production-grade upload platform carries a name that translates to “dummy.” It keeps us humble.

What we actually do

Behind the goofy name is a pragmatic service for handling image uploads: a hardened POST endpoint, Backblaze-backed storage, automatic resizing/watermarking, and delete APIs you can call from any stack. No SDKs, no marketing fluff—just endpoints that work.

• Simple `multipart/form-data` uploads via /uploader/upload.php
• Domain-restricted API keys so you decide who can send files
• XMP metadata embedding for photographers who care about copyright info
• Delete API + dashboards to keep storage under control
• Optional Modal webhook for long-running video processing

Why it exists

I was tired of bolting S3 buckets, signed URLs, and brittle front-end widgets onto every project. Whether you’re an exec who just wants to hand out a link and see every file land in one folder, or a developer embedding the endpoint inside your own app, Tonta gives you a dead-simple way to accept uploads, enforce your rules, and serve files without launching a DevOps expedition.

How we work

• Honest scope: if we don’t ship a feature (SDKs, automation “platforms”), we don’t promise it.
• Transparent docs: everything published at /docs mirrors the live implementation.
• Support by humans: email hello@tonta.io; we’ll actually respond.
• Incremental upgrades: we ship small improvements constantly instead of giant, risky rewrites.

The not-so-secret sauce

We lean on boring, proven infrastructure. It’s not flashy, but it’s dependable—and when your kid names your company “dummy,” you overcompensate by making the tech rock solid.