AI Masters Inventory

Data is stored only in this browser. Export a backup regularly.

How this app works, and how to set up a new product. Screenshots appear once their files are added to onboarding/screenshots/.

How the app works

• SaaS Agency: the agency's own hosting and tools, such as Hostinger and Coolify.
• Products: pick a product, then a client. Each client has its forms (HQ, Production, Staging, Onboarding for in-house clients; Production for others).
• Manage products and Manage clients: add, edit, or remove products and clients.
• New form: create a new form.
• Backup: export or import all data as JSON. Export regularly.
• Sign out (top right) locks the app.

Data is saved in this browser. After the allowed Google account signs in, it is also saved online in Supabase. Only that one account can read or change the online data.

Follow these in order. The full guide is in onboarding/ONBOARDING.md and the Google steps are in onboarding/google-auth.md.

1. Hostinger: add the subdomain as an A record that points to the VPS.
2. GitHub: create a private repository and push the code.
3. Supabase: create the project, run supabase/schema.sql with the allowed email, turn off sign-ups, set the URL configuration.
4. Google Cloud Auth: create the OAuth client in Google Cloud Console, save its Client ID and secret, then enable Google in Supabase.
5. Resend: add the sending domain, add its DNS records at Hostinger, create an API key (server side only).
6. Coolify: create the project and app from GitHub, set the domain, and deploy.

1. Create a new project and save the database password.
2. Copy the Project URL and the publishable key (never the service_role key).

   

3. Open SQL Editor, paste supabase/schema.sql with the allowed email, and run it. Expected: "Success. No rows returned".

   

4. Check Policies: three policies on app_state, RLS on, no delete policy.

   

5. Turn off "Allow new users to sign up" and "Allow anonymous sign-ins".

   

6. Set Site URL and Redirect URLs to the live domain.

   

1. Create a private repository.

   

2. Push the code. Never commit .env files or keys.
3. If needed, create a fine-grained token with Contents: Read-only on that repository only.

   

1. Select the product's Google Cloud project at console.cloud.google.com.
2. Set up the consent screen (External, Testing). Add the allowed account as a test user.

   

3. Create a Web application OAuth client at Clients. Redirect URI: https://<project-ref>.supabase.co/auth/v1/callback. Example for this product: https://zqshuvukyjbrnxcwnfuf.supabase.co/auth/v1/callback (the project ref is the part of the Supabase Project URL before .supabase.co).

   

4. Client ID and client secret: copy both into your password manager. Never share the secret or put it in this page.

   

5. In Supabase, Authentication, Sign In / Providers, Google: turn on Enable Sign in with Google, paste the Client ID and secret, then click Save. The list then shows Google as ENABLED. Until this is saved, the app shows "Unsupported provider: provider is not enabled".

   

1. Add a sending domain (for example mail.yourdomain.com).

   

2. Add every DNS record Resend shows at Hostinger, then verify.

   

3. Create an API key with sending access. Keep it on the server only, never in this page.

   

1. Open the Coolify dashboard over HTTPS.

   

2. Create a project, add an application from the GitHub repository, set the live domain, then deploy.

   

1. Open the parent domain's DNS settings in hPanel.

   

2. Add an A record: name inventory (or the new subdomain), value the VPS IP.

   

3. Keep Hostinger nameservers. Do not use Cloudflare for DNS.