pjullrich

It does already, but it's not yet properly documented. You can already run your own Gitea runner and point it at Pushin. I'll also add managed CI runner support based on Firecracker VMs soon. Currently, I use self-hosted runners for my CI, but the UI is a bit rough. I wanted to merge a PR today that fixes all that but then HN happened so just bear with me a little longer :)

I think you should be able to do that if you run your own Tangled knot. I'd assume that you can host it under your domain which means your git service will remain even if Tangled itself is down or goes under.

Thank you! I hope the key shortcuts help too! I took that inspiration from npmx.dev :)

Even though we don't have a dog tax in Leiden, NL, where I live, Bella is certainly taxing being the 2yo Labrador pup that she is :D

- and I agree!

You can sign-up and I'll invite you to a chat room I'll set up based on chatto.run very soon. That'll be my main outlet for news and announcements.

You're free to use the API from your LLMs or other automations and push LLM-generated code, but not blast maintainers with your slop-machine.

That’s right. There are plenty of good options for OSS but few to none focused on both, public and private especially with team/enterprise support. That’s why I created Pushin :) simply to have a place to store both my public and private repos but still retain a community which you dont get on a self-hosted solution

Yes! I’d love to provide private or at least personal firehoses to users maybe based on the same lexicons as Tangled uses so that you can sync your Pushin repo to your own Tangled knot. That’d be cool, no? Also, sign-in with your atmosphere account, and generally offering lexicon-based API output to make it easy to sync to Tangled or somewhere else

Mostly her toys which I should throw without first taking them. Only throw, no taking

It's closer to walgit as it stores the packs in S3, but it uses Postgres for locking a repo during a push instead of using the Cursor/Walgit trick of using a WAL+CAS in S3. I've evaluated CAS on the Scaleway S3 service, but writing the WAL adds 240ms to every push, a cost we don't have with Postgres where it's a fast row lock. I also evaluated whether keeping a WAL would be useful, but ultimately decided against it because we can track everything the WAL tracks through the git history + audit logs without the write cost overhead.

Oh wow! I'll start pushin (pun intended) to get this ready in time for you to switch then :)

yes

Thank you and I absolutely agree! Pushin is merely one building block. We need a European-centric push in many products.

Yes.

Wenn du willst kann ich auch alles auf Deutsch schreiben aber dann versteht's keiner

I'm very much aware of that and I've put all my effort into making the application trustworthy first. That means: Not a single byte must ever get lost. Since the website wasn't updated for the general public when it hit HN, these trust signals (e.g. privacy policy, ToS, info on business model) are/were missing. Sorry about that!

I just added a new FAQ item for that, but I'll copy it here as well:

We plan to reduce low-quality contributions through several features, some already in place and others still to come. Invite-only registration helps us discourage low-quality accounts and confirm that new members are real people. Next, we plan to introduce a vouching system, similar to Tangled's, that lets contributors build a reputation. We'll combine that reputation with other signals to assess new pull requests and issues. Contributions that appear low quality will be clearly marked and de-emphasized, while maintainers will make the final decision. We also plan to limit how many pull requests and issues a new contributor can open in repositories they don't own. This will be an ongoing effort, but the goal is simple: maintainers stay in control of their queues.

Thank you!

I self-hosted Pushin on my own Forgejo instance on a Hetzner bare metal server before Pushin was ready and it was a great experience to be honest! Self-hosting Forgejo is great!

Thank you, but what? The name was meant like: `Push in (Europe)` hence, pushin.eu

It has brought me joy for almost 9 years now and I wouldn't trade it for the world! :) Glad that you enjoy it too!

"Track" means "store" here and we need to store it for authentication (email+password hash) and to show your public profile (e.g. https://pushin.eu/pjullrich). So, regular things, not tracking you for data mining stuff

Yes, we can't block models from scraping the public repos and train on them, but *we* won't use your code (neither public nor private) to train models on them. We really only want to host your code and do that well.

Yes, that's my test organization :)

I was never really blockchain-something. It was all the hype when I finished my software engineering masters (around 2017/18), so to understand the technology better I started a Podcast and wrote my master thesis about it. I never used it or worked in it afterwards though and I never thought it'd become more than a scam unfortunately

It will!

I'll introduce subscriptions soon, we're currently still in invite-only beta, but the subscriptions will be very much like GitHub/GitLabs with individual and team pricing.

Thank you! Sorry about that, this post on HN caught me before it was ready. Upload limits are: 5GB for logs, 5GB for artifacts, 10 GB cache. These limits will probably change once I introduce a paid trier (same limits there, lower limits on the free tier)

Yes, sorry this escaped containment before I was able to update the landing page. Since the product is in invite-only beta still, I focused on the UX of the platform instead of the "marketing materials" aka. Landing page

That's true, that's me! My personal website is peterullrich.com

Hi, Peter the Founder of Pushin.eu here. Sorry, the website escaped containment and landed on HN before I had the chance to update the "marketing materials" aka. landing page. So, here are a few points:

*The product is stable, but still in development. That's why some of the core things like pricing, etc. are missing. BUT:*

1. Business Model: Pushin will have subscriptions for individuals and teams. Pricing is not yet decided but it'll be close to GitHub/GitLab pricing.

2. Privacy: In true German fashion, we *don't* want your private data. Pushin doesn't track anything beyond the obvious: email, password hash, username, whatever information you put on your profile.

3. Roadmap: We're currently in Beta, but everything looks good so far. We'll probably go GA beginning of 2027. I'll focus on delivering the core features first and make sure that they are polished and of good quality before moving on to the nice-to-haves.

4. I say "we" but it's really only me (Peter Ullrich, peterullrich.com) and my dog (Bella, Labrador, beige). "We" are not VC funded, but bootstrapping on bare metal Scaleway servers. My wish is for this to become a proper company soon though.

5. Tech-stack: Elixir (Phoenix + LiveView) for most parts, Rust for the Git parts, S3-compatible buckets and Postgres on Scaleway, servers are bare metal Scaleway servers running in Paris.

6. Git implementation: Just like Tangled, I've used Rust and the gitoxide libraries to build a Git implementation that's fully compatible with the canonical Git CLI, but uses S3-compatible buckets as storage instead of keeping the entire repo on disk. I'll write in-depth about this soon, but it's very much what Tangled did, just with a different storage concept.

I gotta be honest that I'm both scared but also excited that Pushin hit HN. I wish we'd be better prepared, but here we are. Many thanks to anyone who is willing to try it out!