A project I valued.
An idea worth continuing.

Where it started

I’m Simon Peter Rothgang, an Information Systems master’s student from Münster, Germany. I used Gophish during my master’s thesis and really appreciated the project and what it made possible.

I was disappointed by the lack of ongoing maintenance. There were things I wanted to improve from my own experience, and ideas in the Gophish issue tracker that I wanted to explore. I decided to build on the workflows I liked and give the project a new direction.

What I’m building

Ruphish is my independently maintained successor: a native Rust backend and a new Rust/WASM administration interface. Its direction comes from practical experience, features I wished I had during my thesis, and requests raised by the Gophish community.

The focus is on understandable campaign workflows, useful reporting, and careful handling of participant data. The supported tracking model records interaction events and optional presence indicators. It does not offer collection of participant-entered credentials or arbitrary form values. The participant-data guide explains the model and its implications.

Built on a contribution I respect

Gophish made phishing simulation accessible to many people, including me. Ruphish acknowledges that foundation and preserves attribution for reused material. This is an independent project, without an official affiliation with the Gophish maintainers.

Follow the work

Ruphish is under active development. The current starting point is a source build and a local Docker exercise; downloadable releases are not yet the documented installation path. The docs describe the current source and distinguish supported workflows from compatibility differences.

You can explore the source, share an issue or a feature idea, or try Ruphish locally.