joaoh82

Interesting! I'll take a look.

About monetization, that is definitely very important. For now, and not sure how long, could be days or weeks, I am offering api-keys at no charge, because I want the feedback of real users. But obviously that is not sustainable in the long term, servers cost money and monetization also help keep the project alive.

At a second stage, I am planning to offer monthly or yearly plans with different limitations or unlimited also. But I am also planning on offering pay per use with short lives api-keys targeting agentic workflows, for example or people that dont really want to pay a monthly fee, but instead just cents for a short-lived tunnel.

For the monthly plans, I am planning to keep as low cost as possible, just enough to maintain the infrastructure and development + some overhead.

that is a very good use case. I am definitely adding this to the roadmap at least a maybe.

Thanks for the question.

Very good points. Including the AGPL, that is definitely a better license for this type of project. I am just used to starting with MIT when I start a new open source project, but you have a point.

About monetization, that is definitely very important. For now, and not sure how long, could be days or weeks, I am offering api-keys at no charge, because I want the feedback of real users. But obviously that is not sustainable in the long term, servers cost money and monetization also help keep the project alive.

At a second stage, I am planning to offer monthly or yearly plans with different limitations or unlimited also. But I am also planning on offering pay per use with short lives api-keys targeting agentic workflows, for example or people that dont really want to pay a monthly fee, but instead just cents for a short-lived tunnel.

For the monthly plans, I am planning to keep as low cost as possible, just enough to maintain the infrastructure and development + some overhead.

For now is free. And when we start charging will definitely be cheaper. Also, the project is open source and there is good documentation on how to standup your own infra, if you want to go down that path.

Hey! it does support subdomains. Either by passing a flag --subdomain or just configuring them straight up in you config.yml file.

We also implemented auto-reconnect.

For now we only running servers in Europe, but we are implementing multi-region right now and should have it up in a couple of days. That should cut latency way down for people that not in Europe.

Nice! Will do!

Btw, if anyone wants to test on our own servers just request an api key with github issues: https://github.com/joaoh82/rustunnel?tab=readme-ov-file#gett...

A ngrok-style secure tunnel server written in Rust. Expose local services through a public server over encrypted WebSocket connections with TLS termination, HTTP/TCP proxying, a live dashboard, Prometheus metrics, and audit logging.

I tested plenty and the console logs in the UI is a game changer. Super slick.

The definitive directory for Model Context Protocol (MCP) servers. Discover, install, and contribute to the AI integration ecosystem.

Screen Console is a logging tool made for Godot 4 that allows you to print messages to the screen for debugging and development purposes.

thanks for the tip man. I think you are right. Rust data structures might do the job at first, specially for in-memory operations. But on-disk storage if definitely going to be a problem.

I wouldn't mind partnering up with Mozilla on this. Hey Mozilla!!!