RimbraDocs

Account and billing

Your sign-in, your workspace, your plan and your usage.

Your account

  • Your account owns one workspace with everything you create.
  • Signing out ends the session on that browser. It never deletes anything.

Plans

FreeLaunchProScale
Price per month$0$5$15$49
Projects41230100
Databases151030
Build minutes a month2001,0003,00010,000
Builds at the same time1238
Storage (files and databases)10 GB30 GB75 GB250 GB
Outbound bandwidth a month50 GB100 GB200 GB1,000 GB
Emails a month1,0007,00020,00075,000
Social notifications a month3,00010,00025,000100,000
Custom domains11025100
Memory per project512 MB1 GB2 GB4 GB

Usage

Billing → Usage shows how much of each limit you have used in your current cycle. Each cycle starts on the day your workspace signed up and repeats on that date every month, so build minutes, emails, social notifications and bandwidth are counted from there. There are no daily limits. The Overview page warns you at 80% and when you reach a limit, and add-ons raise a limit straight away.

Paying

  • Upgrades, add-ons, domains and numbers are paid at a secure Bachs checkout by card, bank transfer or other local methods. A small processing fee is added at checkout and depends on how you pay.
  • A paid plan covers a month, or a year if you chose yearly. Billing → Plan shows the date it is paid until. We email you 3 days before; renewing adds the time on from that date.
  • If you don’t renew, you keep the plan for 7 more days, then the workspace moves to Free. Nothing is deleted, and anything over the Free limits waits until you upgrade again.
  • An invoice from us (for a custom plan, for example) comes by email with a link to pay by card or bank transfer from any Nigerian bank.
  • Put the invoice number (for example RIM-202610-0007) in the transfer description. The invoice is marked paid within minutes of the transfer arriving and you get a receipt by email. If you forget, contact support with your bank receipt.

Keep your workspace safe

  • Keep API keys and database URLs in environment variables, never in code.
  • Use one key per app and revoke keys you no longer use.
  • Rotate a key straight away if it ever ends up somewhere public.