FilesHub: the plumbing every app needs, behind one key
- Web
FilesHub sits beside your own backend, the server side of your app: file storage, transactional email and small utility endpoints, all behind one API key. Access is by request. We built it to run our own apps, and it still does.
What is FilesHub?
One shelf for the jobs every new app signs up for again. Each project keeps its own files, public or private, and a public file gets a stable link you can drop straight into an image tag.
Transactional email, the messages an app sends one person at a time, goes out with templates, schedules and a log of what was sent. Short links, QR codes, PDFs, one-time codes and webhooks sit beside them.
Who is FilesHub for?
Developers starting an app who’d rather not open a fifth dashboard. Your main backend keeps the product logic. FilesHub holds the utilities.
What did we build?
Keys that know their limits. Each one is scoped twice: by permission, which decides what it may call, and by allowed origin, which decides where it’s called from. Approval comes before any project or key, and each app gets its own project and its own key.
On request there’s a Project Vault: an encrypted place per project for credentials and config files. Values stay hidden until someone reveals one. Each reveal is recorded.
We also wrote the API down for machines: an integration spec in JSON and Markdown that a coding agent can read and wire in.
Where can I check it?
Try a request from its Postman collection before you write any code, then ask for access.
Want something like FilesHub built?
A backend with keys, quotas and a dashboard of its own is work we do for clients too, and Web apps shows how it runs.
Bring the brief if you know which services your app leans on, or sort that list with us in a free consultation.
Page updated .