goca

Support

Get unstuck

Support for goca (the ngca engine): an assistant that has read the manual, public bug reports with a status trail, and paid engineering help when the project is funded.

AI chat

Ask the assistant first

It has read the entire operator manual — and it will tell you when the honest answer is “that isn’t built yet” rather than improvising one.

checking assistant status…

online — the answering bot is connected (heartbeat within the last minute) and replies land in this window. offline — your message is stored and answered when it reconnects; the conversation survives page reloads in this tab.

Start a conversation

Exact error messages beat descriptions of error messages.

Chat traffic is relayed to the maintainer, who reads all of it.

Bug reports

We want the refusal message, not a paraphrase

goca fails loudly and precisely on purpose. The exact text of what it told you is usually most of the diagnosis.

What to include

  • The exact error or refusal message — copied, not retyped from memory.
  • The output of ngca version.
  • Your deployment shape: Compose all-in-one, distributed Compose, or Linux standalone.
  • What the status board showed at the time (/v1/status/components).

Reports that also include /v1/audit/verify output and component status get fixed faster — they let us reproduce instead of guess.

Filing a report returns a public status link: an unguessable URL that shows the title and status history only — never the report body or your email. Bookmark it; it is the only way back to your report.

File a bug report

Stored with the report; never shown on the public status page.

Error text, ngca version, deployment shape, status-board state.

Donations

Fewer untested code paths

goca is developed independently. Donations keep the hardware test bench stocked — real HSMs, real YubiKeys — so “verified on real hardware” stays a sentence this project gets to keep writing.

No tiers, no perks, no logo wall. Just fewer untested code paths.

Donate

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.

Evaluating during free early access? That is exactly what the training center and the assistant 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.