Your clients' data, on your own accounts.
Forge builds custom software for people businesses - agencies, accountants, lawyers, consultants, recruiters. When you let anyone near your clients' files, invoices and messages, the first question is the right one: is this safe? Our answer starts with where the software lives. We don't run it on our accounts. Everything we build runs on accounts your firm owns, so your data stays with you, and we work inside it with access you give us and can take away.
2-week ops audit · nothing technical on your side · runs on your own accountsYou own the accounts, the software and the data. We're the people you let in to look after it.
Your accounts, your data, our care
Most software companies keep your data on their systems, alongside everyone else's. We work the other way round. The tools we build run on accounts set up in your firm's name, so your clients' information never sits in a shared pot with another firm's.
Our team works inside those accounts to monitor, fix and improve what we built, using access you grant. If you ever want to part ways, nothing has to be moved or exported - it's already yours. You simply remove our access.
That means the question "what happens to our data if Forge disappears?" has a boring answer: nothing. It carries on running where it already lives.
The promises, in plain English
You own it
The software and the data live on accounts in your firm's name - not ours.
You control access
You decide who on our team can get in, and you can remove that access at any time.
Kept separate
Your clients' data is never mixed with another firm's, because it never leaves your own accounts.
Passwords and keys handled carefully
Keys for tools like Stripe or your email are stored in your accounts' own secure settings, never in a document or a chat message.
Checked before it goes live
Every change we make is reviewed and tested before your team or your clients see it.
Your brand, not ours
Your logo, your domain. Clients only ever see your firm's name, never Forge's.
What happens to a key you connect
- 1
You create it
When a tool needs to talk to Stripe, your email or another app, you or we create a key for it inside your own account.
- 2
It's stored in your accounts
Kept in the secure settings of the accounts you own - never pasted into a spreadsheet, email or chat.
- 3
Only the tool that needs it can use it
Each tool gets the keys it needs and nothing more.
- 4
You can change it any time
Swapping a key means setting a new one; the old one stops working straight away.
Happy to walk you through it
Security questions are different for every firm - a law firm's are not an agency's. During the ops audit we look at what data the new tools will touch, who on your team should see what, and what your clients expect from you. Then we build to that.
If your firm has its own security questionnaire or IT policy, send it over. We'd rather answer it properly up front than have it hold things up later.
Frequently asked questions
Where does the software actually run?
On accounts your firm owns. We set them up in your name (or use ones you already have), build the tools there and look after them there. We don't run your software on our own accounts.
Can Forge or another firm see my clients' data?
Another firm can't - your data never leaves your own accounts. Our team can see what's needed to look after the tools, using access you grant, and you can remove that access whenever you like.
What happens to the keys and passwords we connect?
They're stored in the secure settings of your own accounts, and each tool only gets the keys it needs. We never ask you to send them in an email or chat, and you can replace any of them at any time.
Do I own my data and my brand?
Yes. The software, the data and the accounts are yours. Your tools carry your brand on your domain, and you're never locked out of your own information.
What happens if we stop working with Forge?
Everything keeps running where it already lives. You remove our access, and the software and data stay with you.
Can you work within our IT or security policy?
Yes. Send it over before the build starts and we'll build to it - and tell you plainly if anything in it changes what we'd recommend.