Rebuild the
possibilities.
For the people who see a game and ask,
“How does that work?”
Discover community-built Rust projects. Turn observations into a spreadsheet, build from evidence, and share what you create.
Creators host. Players connect directly. No game traffic relayed.
ILLUSTRATIVE WORKFLOW · NOT A LIVE BUILD
Find your next project.
Explore reviewed Rust games and the creators building them.
02 / BUILDGo from curiosity to code.
Get the workbook, research method and an example you can run.
03 / CONTRIBUTEMake the tools better.
Improve a guide, reproduce a bug or take on a focused contribution.
Small beginnings.
Wide-open possibilities.
Opening the project index…
Only moderator-published projects appear here.
Connecting to the moderated project index…
A workflow you can
actually follow.
- 01
Observe.
Choose an authorized reference. Record repeatable behavior, sources and what you still don’t know.
- 02
Model.
Turn supported facts into stable IDs, fields and rules in your workbook. Keep hypotheses separate.
- 03
Build.
Validate the matrix. Make an original implementation that consumes your data, not scattered constants.
- 04
Verify.
Compare actual runtime behavior with your observations. Repeat, measure and document the gaps.
Your server.
Your connection.
We help people find the project. The creator runs it.
Direct connection. RustPorts is not in the traffic path.
- Text details and public GitHub links only
- No user game uploads, binaries, assets or server hosting
- No game proxy, relay, tunnel or server inspection
- Every listing goes through moderation
Self-hosting does not remove copyright or other legal responsibilities. Only share work you have the right to share.
Read the connection guide ↗Worth a
closer look.
Pick projects you want to follow. Public activity shows project names, not the GitHub usernames of people picking them.
0 public picksLoading community activity…
Good questions.
Is RustPorts finished?
Not yet. The directory is live and the experimental Python workbook starter is runnable. The native Jcode integration is an unfinished development snapshot. We hope to complete the broader workflow soon, but there is no promised release date. See what is ready and what is next.
Do I need a server to list my project?
No. A public GitHub repository and project details are required. A direct server address is optional. If you offer one, you operate it yourself. Players follow your repository’s instructions and connect in the game’s own client.
What can I submit?
Rust game projects you have the right to share. Submit text details, a public GitHub URL and optionally your own server address. No game files are uploaded. Listings stay private until review, and edits return them to review. Read the submission terms.
Does rewriting something in Rust make it legally safe?
No. Rewriting, parody and self-hosting do not automatically grant rights or remove liability. Use original or properly licensed material, document permissions, and get qualified legal advice when needed. Report a rights concern.
Your next experiment
starts here.
The tools are open. The next idea is yours.