Every web app you build on GenVibe can have its own database, sign-in and file storage, with nothing to set up. Here is how much each plan includes, and what happens when an app reaches it.
Standard 1000 has the numbers of Standard 500, and Standard 2000 those of Pro. Yearly plans have the numbers of the same plan paid monthly.
When you already have as many as your plan includes, publishing one more is refused, with a note that says why. To publish it, upgrade, or delete one of the others: its site stays online for 7 days, then it is removed with its database and files. The apps you have keep working.
When an app’s database is full, that app turns read-only: people can still open it and see everything, but new saves are refused. It works as before once it is under the limit again, after you remove data or upgrade. Nothing is deleted.
This counts the files people upload to your apps. When they reach it, each of your apps that stores files turns read-only: pages and files still open, new uploads and saves are refused, until you delete files or upgrade. The files you add to your projects yourself (a logo, photos) have the same amount again, counted on their own; when that is full, adding one more is refused.
A larger file is refused when you add it.
Your app refuses a larger upload with the message “The file is larger than 10 MB”. Nothing else changes.
Every page, picture and data call that reaches an app with its own database counts as one request, from the 1st of each month (UTC). When your apps reach the number, they turn read-only: they still open and show everything, new saves are refused. At three times the number they are switched off and show a short page saying so, until the 1st of the next month or until you upgrade to a plan that covers them. Nothing is deleted.
Each person counts once, whether they sign in with an email code or with Google. When an app reaches its number, a new person who tries to sign up is told the app is full for now; everyone who already has an account keeps signing in, and the app turns read-only until you upgrade. Paid plans have no fixed limit: a fair-use guard of 1 million people per app, far above any real app, works the same way.
Each one carries a six-digit sign-in code. When an app has sent its number for the month, people who ask for a code are told the app can’t send more sign-in emails right now. Signing in with Google keeps working, everyone already signed in stays signed in, and the count starts again on the 1st (UTC). The app itself is never switched off for this.
Jobs beyond the number are kept and listed in the project’s Jobs panel, but not run, and no job runs more often than the plan allows. Free runs none: a job in a Free project starts running once it is published on a paid plan. A read-only or switched-off app runs no jobs, and each run counts as one server request.
We email you when your apps get near a limit (80%), when an app turns read-only and when apps are switched off, at most one email of each kind a month. Usage is checked every day, so a change can take up to a day to show, and each project’s Limits panel shows where it stands.
Your apps move to the Free numbers. Your oldest app with its own database keeps working and newer ones turn read-only, and an app over a Free number turns read-only too. Nothing is deleted, and upgrading again brings them back.