Jamstack authentication: passwordless login for static websites

Which account features can a static website offer?

Examples include a saved reading list, preferred lesson track, dashboard layout, or compact progress record. Your product defines these experiences; Gammal Tech supplies sign-in and storage rather than automatically creating a complete membership application.

Set up the owner, project, and website domains

The project owner needs a verified Gammal Tech account. Create the account once using passport verification, or an Egyptian national ID where applicable, then open the Developer Console.

Create a project and register the HTTPS domains where the site will operate. Up to four domains are supported. The main domain, its www version, and additional subdomains count as distinct registrations.

The website integration uses the project identifier and registered domains without developer API keys to manage. Check your actual deployment during setup, including its browser behavior and security settings; a static hosting label alone is not a guarantee that every configuration will work unchanged.

How returning-user preferences work

After sign-in, the site can retrieve information previously saved for the same account in the project. Storage is free with a maximum of 1 MB per user. It is useful for small personal records, not a promise of unlimited media or document hosting.

The active session is kept per browser tab. A fresh tab or reopened browser requires sign-in again, while saved data persists. Make this distinction clear so visitors understand why signing in again does not mean their work has disappeared.

The login flow does not give your site the user’s email address, phone number, or identity. Personalization can rely on saved preferences instead. If your website needs a display name or another detail, ask for it separately and explain its purpose.

Public pages and private access are different

Adding a sign-in button does not turn publicly available static files into protected content. A hidden section or disabled button is a presentation choice, not proof that someone has permission to access a paid resource.

For a member-only download, administrator action, or paid entitlement, plan appropriate trusted access checks. Do not rely on a preference the visitor can edit as the sole authority for access.

Likewise, adding Gammal Tech does not automatically link an older customer database. If your static site replaces another account system, design the account-linking or migration process separately. The same care applies to drafts: make save status clear rather than assuming a popup protects unsaved work from every interruption.

Pricing and operating needs for a static site

Currency guide: Listed EGP prices are the billing amounts. USD figures are approximate, using USD 1 = EGP 51.78, the calculated midpoint of Banque Misr’s USD buying and selling rates on 24 September 2026. Your payment provider’s exchange rate and fees may differ.

Login, logout, and session verification are free, as is user data storage within the 1 MB per-user limit. Your first project is free; additional projects have a one-time fee shown through the account.

Each project has 200 OTP codes per month for login and checkout identity verification, then pays 0.40 EGP (approx. US$0.0077) for each additional code. Top up the personal wallet and transfer funds into the project balance for paid usage. Paid OTP operations stop if that project balance is exhausted.

Before launch, test the published HTTPS site, sign-in cancellation, a returning user, another device, and sign-out. Keep hosting costs and any extra paid features separate when estimating your total budget.

Common questions