B2B software for licensed and regulated cannabis operators: point of sale, membership management, inventory, audit trails and reporting exports. Software only – Budify does not sell cannabis.
Tickets, Doku, Zeiterfassung und Kundengespräche an einem Ort, durchsuchbar per KI. Für Softwarefirmen mit Kundenprojekten. Open Source: auf deinem eigenen Server oder in unserer Cloud in Deutschland.
Open-source CRM for teams and AI-powered work. Use the app, ask the built-in chat, or connect external agents through 39 MCP tools. Self-hosted, you own your data.
Scale customer support, sales & recruitment with Bolna Voice Agents. Inbound and outbound calls in vernacular Indian languages like English, Hindi, Hinglish.
8h +2★ 808Business
Site preview image
Do you operate this project?
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Organization repository · verify with a repository file
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Budify Global – compliance-aware multi-country, multi-language site
B2B marketing and lead-gen site for Budify (software only). It never sells, promotes or facilitates the sale of cannabis. Next.js 15 (App Router) · TypeScript · Tailwind · next-intl · static generation for every locale (22 locales, 10 markets).
Status: DRAFT. All legal text, compliance values and translations must be reviewed by qualified local counsel / native reviewers before launch. See docs/COMPLIANCE-ASSUMPTIONS.md.
Quick start
npm install
cp .env.example .env.local
npm run dev # http://localhost:3000 (redirects to your negotiated locale)
npm run check # compliance + i18n + content-lint gates
npm run build && npm start
npm run build runs check and writes public/compliance-audit.json (config version + hash per deployment).
How it works
Concern
Where
Rules per market (min age, consent model, links, footer text, legal pages, positioning, currency, data region)
Language switcher / region selector (header + footer + /regions) stores the choice in bud_locale; once chosen, the site never auto-redirects again. Geography never blocks access.
Add a country
Add a market block in compliance.config.json (copy the closest one; fill every field incl. openQuestions).
Add its locales to languages if new; add src/i18n/slugs.json entries (optional).
Add content/pricing.json currency, content/entities.json entity/representative placeholders, and sub-processor regions if needed.
Add a legal template set / jurisdiction section in src/lib/legal/templates.ts (marked Draft).
npm run check (validates invariants: footer text, privacy link, banned claims, min age, consent model, legal pages).
npm run assumptions and send docs/COMPLIANCE-ASSUMPTIONS.md to local counsel.
Add a language
Add the language to compliance.config.json → languages (name, dir ltr|rtl, font subset) and to scripts/i18n.config.json (full or core).
Create messages/<lang>.json (copy en.json; core languages need only the namespaces listed in coreNamespaces). Keep _meta stating translation status.
Add the language to the relevant market(s) languages. Add a font subset in src/app/layout.tsx if the script needs one.
For RTL (e.g. he-IL) set dir: "rtl"; layout uses logical properties but needs a visual QA pass.
npm run check – fails on missing keys / placeholder mismatches in full languages.
Update compliance rules
Edit compliance.config.json, bump version; bump consentVersion if consent categories, purposes or vendors changed (forces re-consent). Run npm run check; the audit log records the new version on the next build. Never loosen bannedClaims without counsel sign-off.
Verify hreflang/x-default, canonicals, per-locale sitemaps; then set ALLOW_INDEXING=1.
Verify ad-platform policies before running any ads.
Only publish claims you can evidence (integrations, security, certifications, case studies).
Visual style per market (visuals)
Each market in compliance.config.json has visuals: "sa" (default – the photographic, cannabis-themed look copied from budify.co.za: tabbed feature photos, lounge photo, member-app screens) or "neutral" (abstract, text-only illustrations). The sa photos are AI-generated images hotlinked from readdy.ai (see content/sa-visuals.json). Self-host them (avoids third-party requests before consent): run npm run fetch-images on a machine with normal internet access, commit public/sa/, redeploy. Counsel must approve cannabis-themed imagery per market (global.cannabisImageryApproval; STRICT_LAUNCH=1 fails until it is filled in). New sa.* strings are English-only until translated (other languages fall back to English).
Content rules (enforced by content-lint)
No product/consumption imagery, strain or price listings, health claims, or youth-appealing content. Image tags come from content/images.manifest.json and must be in allowedImageryTags. Banned terms are per market and global.
Article translations
content/articles/translations/<lang>-<cc>.json hold machine-translated drafts of the country articles (es, fr, de, it, nl, th, af, zu). They are served for the matching locale's language and linted against that language's banned terms. Have a native-speaking professional/counsel review them before launch. Locales without a translation (e.g. ca-ES) fall back to English with a notice.
