GoFormX / Personal product

One home for forms across your sites.

Deployed · evolving

A form backend and shared inbox, built to fit the AI tools developers already use.

Go / PHP / Waaseyaa / PostgreSQL

GoFormX homepage with the headline ‘One home for your forms’ and an illustrative shared inbox of synthetic submissions. — Live homepage / September 30, 2026

01 / The problem

The problem

Launching another site should not mean building another form backend or losing track of another inbox. I started GoFormX to collect and manage forms across the sites I build.

02 / Constraints

Constraints

Collection must work independently of an AI provider. Public websites need a safe submission endpoint, while management and inbox access stay scoped to the right account.

03 / My contribution

My contribution

I shape the product direction and develop the Go submission service, Waaseyaa control plane and integration contracts.

04 / Decisions & tradeoffs

Decisions & tradeoffs

Go owns schemas, immutable versions and submissions. The PHP control plane owns human accounts and the inbox. A documented API is the foundation for assistant integrations, so the account and forms can outlive a particular tool.

05 / What is demonstrated

What is demonstrated

A local journey collected submissions from two sites into one authorized inbox. The September 30, 2026 deployment separately verified HTTPS, account signup, login, dashboard and logout.

06 / Limitations & current work

Limitations & current work

Deployment checks do not establish production first-use acceptance. Assistant compatibility and notification delivery need their own qualification; mail was deferred at deployment.

Explore the project

Visit GoFormX Go service source

Product direction and local journey, September 29; deployment record, September 30, 2026.