← Back to Can I sign in with Google or Apple?
Can my app have its own users who sign in?
Short answer
Yes: people sign in to your app with GilbPlatform by an e-mail code, and each gets their own vault; your app keeps no passwords.
Before you start
Words used here (1)
- GilbPlatform
- GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Deeper
Also asked:
Does my app keep my users' passwords? No. People sign in to your app with GilbPlatform by a code sent to their e-mail, so your app keeps no passwords and needs no list of users.
Do I have to build the sign-in myself? No. For an app on GilbPlatform, the first step sets up a ready-made core app with a sign-in, and Agent.Coder uses GilbPlatform's ready-made sign-in card before it writes new code.
An app on GilbPlatform does not keep its own users or its own copy of their data. A person signs in with GilbPlatform, by a code sent to their e-mail, and your app then reads and writes in that person's vault, the place where their records are kept. A new person also chooses a vault name, and GilbPlatform makes their vault; someone who already has one signs in with it, without a second vault. So your app needs no list of users and keeps no passwords.
You do not build the sign-in yourself. For an app on GilbPlatform, the first step sets up a ready-made core app with a sign-in, and GilbPlatform's library of ready-made code holds a sign-in card that Agent.Coder, the agent that builds apps, looks for before it writes new code. Each person's things stay in their own vault, so one user does not see another's unless that person shares them. This is for an app, not a website: a published website cannot read or write vaults, so it cannot sign people in to them.
Each person sees only what they may reach: their own vault, and what others have shared with them. Your app gets no more than the signed-in person can. To work in a vault of yours, such as a shared list your app shows everyone, a person needs access you give them, or your app's server reads it for them; the developer answer How does my app's server read its own vault? tells how.
When Agent.Coder, the agent that builds apps, builds an app that signs people in and puts it live at its own web address, it first asks you how long a person should stay signed in: from 5 minutes up to 14 days, and 14 days if you do not choose; each renewal starts the time again. It also gives the app a button to sign out, which ends that sign-in on that device and its renewal at GilbPlatform; it does not sign the person out of other devices or of GilbApp. The platform lets that one web address sign people in on its own. Staying signed in this way works in a web app only: a phone app installed from an app store does not get it, and a person there signs in again with a new code after 7 days. The developer answer How do I choose how long people stay signed in to my app? tells more.
The people who use your app pay MyJackfruit nothing for their own vault, unless they need more space for their own files; MyJackfruit's Pricing page marks its prices as provisional. See: Do my app's users pay anything?
For developers, the steps are in How do I sign in from my app and return the person to it? and How do I use the sign-in kit?
This answer is written for a computer screen.
Source: Live help pages, shared word for word where the same fact: What can I build on GilbPlatform? (does not keep its own users or its own copy of their data), How do I sign in from my app and return the person to it? (e-mail code; a new person chooses a vault name; without a second vault), How does a browser app get the owner's approval? (What a page can read or write is still only what the signed-in person can.), How does my app's server read its own vault?, How do I use the sign-in kit?, Do my app's users pay anything?, How long do tokens last? (from 5 minutes up to 14 days). Standards read from GilbPlatform on 2026-11-12: Proc_v_i_c_PublishPagesDev steps 1-3 and 8 (ask how long; longest 14 days; default 14 days; a Sign out button; The platform admits exactly that origin for sign-in on its own.), Agent.Coder.AskGoLive. https://myjackfruit.com/ (No user table to build. No passwords to keep., read 12 November 2026). Kai-Zen.ValueDeliveryStepRules.First, Agent.Coder (GilbStack item 7). https://myjackfruit.com/privacy/ (records are not public unless you share them), read 13 November 2026. Live answers, sentences shared: Can I trust what the AI suggests and builds? (a ready-made core app with a sign-in); How do I reuse app code units? (the sign-in card). GilbPlatform 0fc5a548 (https://id.gilb.com/version, read 13 November 2026): src/auth/renewable-sign-in.ts:81-84 (5 minutes to 14 days), :519, :665 (the end moves at each renewal); src/routes/email-auth.ts:440-460; Proc_v_i_c_PublishPagesDev steps 1-2 (the app's owner chooses; 14 days longest and default; 300 seconds shortest); src/routes/sign-out.ts:1-40; src/routes/email-auth.ts:309-316 (renewal only for an exact, approved web origin; a native app sends none); Dev.Guide.SignIn.StaySignedIn (A native app that sends no Origin header gets none either.), TokenLife (7 days); Proc_v_i_c_PublishPagesDev step 3.
Checked against GilbApp d529620.