FAQ
Short answers, each with a link to the full page.
Can I use it for client projects?
Yes. Both licences let you build any number of products, for yourself or for clients, and hand a client the source code of the product you built for them. The tiers differ in how many developers may work with the Keelmint code: Solo is one, Team is up to ten in one company. What you may not do is resell or publish Keelmint itself, or use it to make another template or boilerplate. The full terms are in LICENSE at the root of the repo.
Single or multi organization?
multi serves many customer organizations from one deployment, each with its own members, units, roles and data, with a switcher in the header. single is one built-in organization that everyone joins, for an internal tool or a single-company app. Decide before launch: switching from multi to single is not supported. See Organizations and units.
Do I need Stripe?
No. Leave billing out of product.config.ts and nothing is limited and no Stripe keys are needed. Add it when you start charging. See Billing.
Do I need Google login?
No. It is off until you set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. See Google login.
Can users create their own organization?
Yes, with organizationSignup: { maxPerUser } in the product config: a signed-in user creates an organization and becomes its admin; the first one gets the trial. Without it, only the platform admin creates organizations. See Organizations and units.
Can I remove a feature I don’t need?
Billing and Google login are off unless configured, and self-service signup is off unless you add organizationSignup. The helpdesk (the Support link), notifications (the bell) and the audit log are part of core and always present, in the API and in the layout; there is no switch to turn them off today. Don’t delete core code to get rid of one: it would make every later update conflict. See Updating.
How do I add my own product?
pnpm nx g @core/plugin:product <name>, then follow its first-run steps. See Your product.
Can I use another database?
Keelmint is built on Postgres: the tenant scoping, the job queue (pg-boss), live notifications (LISTEN/NOTIFY) and the migrations all rely on it. Use any managed Postgres 17 (or newer) in production.
Where do emails go in development?
To Mailpit, at http://localhost:8025. Nothing leaves your machine. For production SMTP see Authentication.
How do I get updates?
Merge newer Keelmint releases into your repo; your product code stays separate from core. See Updating.
How do I make the first platform admin in production?
One SQL statement, once: see Permissions and roles.
Which languages are included?
English and Greek, for the UI and the emails. Adding one is a translation file per library, the language list, the database enum and the email templates. See Translations.