I published a research paper. It has a DOI. It's indexed. It's connected to my ORCID. The Mutuus website is live, with the paper, LaTeX source, and an Overleaf integration.
ResearchGate rejected me. arXiv requires an endorsement from someone already in the club. I don't know anyone who publishes papers.
I published anyway.
The Academic Gatekeeping Problem
Research platforms block entry before you've had a chance to prove anything. The bar isn't "produce something worthy." It's "already be someone."
arXiv requires an endorsement. To get one, you need to know a researcher already on the platform who's willing to vouch for you. That sounds reasonable until you realize that most people who'd have a reason to vouch for you are the same people whose work you've cited. Pinging them cold to ask for a favor feels weird. Building a relationship purely to extract an endorsement feels worse.
ResearchGate just rejected me. No explanation. No path forward. Just no.
The frustrating thing is the implicit logic: we'll only accept you once you've already proven yourself, but you can't prove yourself until we accept you. It's the software engineering job market. Entry-level positions requiring five years of experience.
I understand why these systems exist. Academic publishing has real fraud problems. Preprint servers get gamed. Fake papers with generated citations have made it onto platforms. The platforms aren't being paranoid without cause.
But the solution to fraud is removal and accountability, not prohibition. If I turned out to be a charlatan, pull the paper. Flag the account. That's a tractable problem. Blocking every unaffiliated practitioner on the front end to prevent a problem you could address on the back end isn't protecting research quality. It's protecting an incumbent network.
The people this hurts most aren't bad actors. Bad actors find workarounds. It hurts engineers, independent researchers, and practitioners who have real contributions to make but no institutional address to put on a form.
Zenodo Did What The Others Wouldn't
Zenodo let me publish. That's it. That's the whole reason I'm writing this with a DOI instead of a blog URL.
Zenodo is run by CERN. It's open, free, and doesn't require institutional affiliation or someone else's permission. You deposit your work, it issues a DOI immediately, and you're done. The paper is real. It's indexed. It's citable.
I also created a Mutuus community on Zenodo, so future research under that umbrella has a home with some structure to it. That mattered more than I expected. It turned a single paper deposit into the beginning of something.
Building Your Own Front Door
When the existing platforms won't let you in, building your own isn't a consolation prize. It's the better outcome.
The Mutuus website is live at mutuus.bytequilt.com. The paper lives there. Readers can download the LaTeX source or open it directly in Overleaf. The site connects to my ORCID profile. Keystatic handled the content management, same as the rest of the ByteQuilt ecosystem.
That's a better reading experience than ResearchGate would have given me anyway. And I own it.
Keystatic keeps proving itself. Every time I need to extend the content model for something new, whether that's blog posts, research papers, or product docs, it slots in without friction. The Mutuus site required a new collection type for papers with LaTeX metadata and Overleaf linking. An afternoon of work. That's the payoff of owning your content layer instead of renting space on someone else's platform.
The ORCID integration was worth doing early. ORCID is the one piece of academic infrastructure that actually works the way it should: open, portable, not gatekept. You create an account, you own your researcher identifier, and it follows you regardless of what platforms you use or get rejected from.
If you're building a research presence without institutional backing, the stack that worked for me is Zenodo for DOIs and deposits, ORCID for researcher identity, and your own site for everything else. Publish, build your own platform, and let the work speak.
This Is Where It Starts
Publishing the first paper isn't the destination. It's proof that the path exists.
I'm a software engineer who builds databases and design systems and writes a lot of code. I also, now, publish research. Those aren't separate identities. The engineering work informs the research, and the research is already informing the engineering in ways I didn't anticipate when I started.
The gatekeepers I ran into don't get to decide when my journey as a researcher begins. That already happened.