Communication channels

[Gugabit]

I now noticed I haven't presented myself.

Hi, I'm Gustavo, as you now know I am Brazilian and I am taking over a small hotel in the countryside. I was raised in the hotel and went away to become an engineer, I now have +8 years of experience working with healthcare ERP, now I am coming back to manage the family business and I'm trying to modernize things, we still running on pen and paper 😂.

That being said, I have started testing the whole application and fell in love with the way things were built, I tested every open source PMS in the marked but none so far had the business logic I found simple enough or efficient enough, I was even starting to convince myself to build my own when I found HAIP, and with you being committed to Apache 2.0 I really want to help you succeed here, so I want to become an active developer.

For that I would greatly enjoy to hear your plans, features you are thinking about or what you are already working on so our work do not collide, I started with localization since that is something simple, but I have also already found some bugs and improvements I would like to work on if possible, most of them being simply UI bugs, but also some core features like complete guest registration missing (National Identification, Birth date, Address, Responsible tutor in case of minors...etc)

Would you also be interested in creating a discord server for that, or believe it is preferred that comms stay here?

[telivity-otaip]

Hi Gustavo,

Welcome, and thanks — a note this specific, from someone who's actually run the whole market comparison and nearly built their own before landing here, is worth more than a dozen "looks cool" stars. Let's get you productive.

So our work doesn't collide — the roadmap lives at HAIP_BUILD_PLAN.md. Where things stand:

Just landed: a big pass fixing the dashboard↔API contract (forms that were silently failing), the booking widget served in Docker, and the back-office screens.
In progress: production deployment path (compose + images + docs), full dashboard localization, and end-to-end + money-path test coverage.
Planned: onboarding wizard, complete guest registration, loyalty, upsells/ancillaries, revenue management, BI/analytics, and hardening. Plenty of open ground.
On what you raised:

Localization — great start, and there's real work here you could own outright. Today only the shell (nav, header, admin, media) reads from the locale files; most of the 21 page bodies are still hardcoded English. The actual i18n job is wiring t() through those pages and extracting their strings. Mechanical but high-value, no collision — if you want it, it's yours. A pt-BR locale would be a great addition too.

UI bugs — yes, please. Open issues or small focused PRs as you find them.

Guest registration — good news and a heads-up. A lot of what you listed already exists in the data model: the guests table has ID type/number/country/expiry, nationality, date of birth, full address, and GDPR consent. What's genuinely missing:

the minor / responsible-guardian case — you're right, no guardian field yet;
surfacing all of it in the dashboard — the Guests form only captures name/email/phone today, though the API accepts the rest;
Brazil-specific registration (FNRH / SNRHos) — the property table already has a guestRegistrationConfig JSON hook designed for exactly this per-jurisdiction case, so it's built to extend rather than hack.
That's a well-scoped first core contribution, and being Brazilian and taking over a real hotel, you're the right person to get FNRH correct. Two things before you dig in: (1) CLAUDE.md in the repo is the project constitution — note the multi-tenancy rules and that the guests row is cross-property by design; (2) for hotel-domain specifics, don't guess — drop the question in the PR/issue or Discord and I'll confirm the intended behavior. You clearly know hospitality; this is about staying consistent with how HAIP already models things, not second-guessing you.

One thing you may have missed — HAIP has AI built in, and it's public now. It's an optional local model (HAIP AI) that reasons over the deterministic agents' real numbers to explain their decisions in plain language — grounded so it can't invent a rate or a figure, runs entirely on your own hardware via Ollama, off by default. It's Apache-2.0 and on Hugging Face; just ollama pull hf.co/telivity/haip-ai and set HAIP_AI_ENABLED=true HAIP_AI_MODEL=haip-ai (the enable steps are in the README's HAIP AI section). Worth a look — it's a big part of what makes HAIP different.

And on the hosted side, there's Remy — our AI admin copilot. Where HAIP AI explains, Remy operates: it sets up and runs the platform for you (configuration, integrations, even deploying the booking site). It's part of the managed/hosted version and isn't open-sourced because the compute and hosting behind it aren't free — but if you're curious, I'm happy to give you a look so you can see what we've built on top of the open core.

Discord — yes, let's. Now that there are real contributors, it's worth a place to coordinate; I'll spin one up and send you the invite. GitHub stays the record for issues/PRs, Discord for the faster back-and-forth.

Open a draft PR or an issue for whatever you pick first and tag me — I'll make sure we're aligned before you sink time in. Really glad to have you.

Best,
Dusan

[telivity-otaip]

@Gugabit Discord done.

💬 Community & Support

Discord is our main support channel — questions, bugs, feature ideas, or just want to talk to the team? Join us:

👉 https://discord.gg/rJQJ5Rh5kH

For confirmed bugs and feature requests, please still open a GitHub issue so we can track it. For everything else, Discord is the fastest way to reach us. Every commit, PR, and release also posts into the server, so you can follow development in real time.

Dusan