foundryline
Demo mode. This form runs entirely in your browser so you can see how the client area works. It does not create a real account and it stores no password. How to make it real.

Client area

Everything about your project in one place.

Enter the email you gave us, in the form name@domain.com

Enter your password

Forgot your password?

Enter your name

That does not look like an email address

Enter your brand name

Use at least 8 characters

Before you sign up: how we handle your data. We use your details for your project and nothing else.

For the studio, not for clients

This portal is a working interface, not a working login.

Read this before you show it to anyone. The form above validates properly and the dashboard renders from real data structures, but it keeps everything in your browser. That is fine for a demo and it is not fine for real client accounts.

A real login needs a server. Passwords have to be hashed with bcrypt or argon2, sessions need real tokens, and someone has to patch it when a vulnerability lands. There is no version of this that lives in a static HTML file.

Three honest options

1. Do not have a portal yet. Send clients a shared Google Drive folder and a Notion page. Zero risk, ten minutes to set up, and honestly fine for your first twenty clients.

2. Supabase or Firebase Auth. A hosted backend with password hashing and sessions already written. You get email and password, Google sign-in and password reset without writing crypto yourself. About a day of work to wire up, and it is what most small studios actually use.

3. Build it properly. Your own backend, your own database, your own backups. This is a real project — plan on a week, plus ongoing maintenance. Worth it once you have thirty or more active clients.

Do not store passwords in localStorage, in a JSON file, or in the database as plain text. Not even for testing. The habit is what causes the breach later.