Support

Get unstuck

Support for goca runs through one conversation: an assistant that has read the entire operator manual, answers configuration questions, and files bug reports and feature requests for you — each with a public status trail. Paid engineering help below.

Assistant

Questions, bugs, feature ideas — start here

The assistant has read the entire operator manual. It answers configuration questions — and tells you when the honest answer is “that isn’t built yet” rather than improvising one. Found a bug, or want a feature? Say so: it confirms the details with you, then files the report and hands you the public status link.

checking assistant status…

Verify your email

The assistant answers from the goca documentation and files bug reports and feature requests on your behalf. So that a conversation can be picked up again and answered properly, it starts with an email address you can read.

Please use your work address — consumer mailboxes (gmail, outlook, hotmail, gmx, proton and the like) are not accepted here.

What to include

  • Bugs: the exact error or refusal message — copied, not retyped from memory.
  • The output of goca version and your deployment shape: Compose all-in-one, distributed Compose, or Linux standalone.
  • If more than one process is involved: what the status board shows, as text — role, instance, site and state for each row.
  • Feature ideas: not just what it should do technically — also what benefit you expect from it. That context decides how a request is weighed.

None of this is a form to fill in — the assistant asks for what it needs. Reports that arrive with these get resolved faster: they let us reproduce instead of guess.

When the assistant files a report it replies with a public status link: an unguessable URL that shows the title and status history only — never the conversation, the report body, or your email. Bookmark it or add you email on the report page to be notified.

Professional assistance

Paid engineering work

Deployment reviews, custody architecture, migration planning, escalated debugging — scoped, quoted, and done properly.

Tell us the timeline, the scope, and a budget indication. Inquiries that read as funded projects get a reply; inquiries that read as free consulting will not.

Just evaluating? That is exactly what the training center and the chat at the top of this page are for.

Send an inquiry

A range is fine — it tells us which conversation to have.

Timeline, scope, environment. One paragraph is enough to start.