Go Quic

Open-source Go projects categorized as Quic

Top 13 Go Quic Projects

  • gost

    GO Simple Tunnel - a simple tunnel written in golang

    Project mention: Teach us something Sundays | reddit.com/r/ExperiencedFounders | 2023-05-21

    With a combination of Gost and cloudflare tunnel you can access literally anything on the local LAN network.

  • quic-go

    A QUIC implementation in pure go

    Project mention: [Help] once encrypt I cannot access webUI | reddit.com/r/Adguard | 2023-02-20

    2023/02/20 11:30:25.292491 [info] tls config has changed, restarting https server 2023/02/20 11:30:25.294059 [info] Start reconfiguring the server 2023/02/20 11:30:25.294064 [info] Stopping the DNS proxy server 2023/02/20 11:30:25.294103 [info] Stopped the DNS proxy server 2023/02/20 11:30:25.394663 [info] dnsproxy: cache: enabled, size 4096 b 2023/02/20 11:30:25.394675 [info] MaxGoroutines is set to 300 2023/02/20 11:30:25.395544 [info] Starting the DNS proxy server 2023/02/20 11:30:25.395549 [info] Ratelimit is enabled and set to 20 rps 2023/02/20 11:30:25.395551 [info] The server is configured to refuse ANY requests 2023/02/20 11:30:25.395553 [info] dnsproxy: cache: enabled, size 4194304 b 2023/02/20 11:30:25.395570 [info] MaxGoroutines is set to 300 2023/02/20 11:30:25.395574 [info] Creating the UDP server socket 2023/02/20 11:30:25.395609 [info] Listening to udp://[::]:53 2023/02/20 11:30:25.395612 [info] Creating a TCP server socket 2023/02/20 11:30:25.395628 [info] Listening to tcp://[::]:53 2023/02/20 11:30:25.395630 [info] Creating a TLS server socket 2023/02/20 11:30:25.395641 [info] Listening to tls://[::]:853 2023/02/20 11:30:25.395645 [info] Creating a QUIC listener 2023/02/20 11:30:25.395702 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details. 2023/02/20 11:30:25.395943 [info] Listening to quic://[::]:853 2023/02/20 11:30:25.395960 [info] Entering the UDP listener loop on [::]:53 2023/02/20 11:30:25.395993 [info] Entering the tcp listener loop on [::]:53 2023/02/20 11:30:25.396012 [info] Entering the tls listener loop on [::]:853 2023/02/20 11:30:25.396067 [info] Entering the DNS-over-QUIC listener loop on [::]:853 2023/02/20 11:30:25.396635 [info] go to https://local.adguardhome:443 yaml part: tls: enabled: true server_name: local.adguardhome force_https: false port_https: 443 port_dns_over_tls: 853 port_dns_over_quic: 853 port_dnscrypt: 0 dnscrypt_config_file: "" allow_unencrypted_doh: false certificate_chain: |-


    ONLYOFFICE Docs — document collaboration in your environment. Powerful document editing and collaboration in your app or environment. Ultimate security, API and 30+ ready connectors, SaaS or on-premises

  • hysteria

    Hysteria is a feature-packed proxy & relay tool optimized for lossy, unstable connections (e.g. satellite networks, congested public Wi-Fi, connecting to foreign servers from China)

    Project mention: Why won't my self-hosted VPN work? | reddit.com/r/selfhosted | 2023-03-05
  • algernon

    :tophat: Small self-contained pure-Go web server with Lua, Markdown, HTTP/2, QUIC, Redis and PostgreSQL support

  • yomo

    🦖 Streaming Serverless Framework for Software Edge Infra

    Project mention: FireScroll - An unkillable multi-region KV database that scales reads to infinity | reddit.com/r/golang | 2023-05-01

    I have used HTTP3 QUIC for really fast edge. This golang project: https://github.com/yomorun/yomo

  • gost

    GO Simple Tunnel - a simple tunnel written in golang (by go-gost)

    Project mention: Hackers claim vast access to Western Digital systems | news.ycombinator.com | 2023-04-13

    "I'm going to take this opportunity to shill gost, an amazing tool ..."

    Here is the english readme:


    ... and here is a better page:


    It seems to have a rich feature set ... can you elaborate on why you like this tool so much ?

  • quicssh

    SSH over QUIC

    Project mention: quicssh-rs Rust implementation SSH over Quic proxy tool | reddit.com/r/rust | 2023-04-30

    quicssh-rs is quicssh rust implementation. It is based on quinn and tokio

  • CodiumAI

    TestGPT | Generating meaningful tests for busy devs. Get non-trivial tests (and trivial, too!) suggested right inside your IDE, so you can code smart, create more value, and stay confident when you push.

  • kawipiko

    kawipiko -- blazingly fast static HTTP server -- focused on low latency and high concurrency, by leveraging Go, `fasthttp` and the CDB embedded database

    Project mention: Static site hosting hurdles | news.ycombinator.com | 2022-09-05

    [the author here] Indeed didn't mention anything about the shared webhosting solutions, just as I didn't mention anything about S3 + CloudFront, or Backblaze B2 + a CDN in front, or Cloudflare + WebWorkers, or AWS Lambda, or any other thousand ways to do it... (Like for example there is <https://redbean.dev/> which I find just so intriguing, and not far from my own <https://github.com/volution/kawipiko> proposal.)

    Although shared webhosting is part of our web history -- and still a viable choice especially if you have something in PHP or something that requires a little-bit of dynamic content -- I don't think it's still a common choice for today.

    It's somewhere in between dedicated cloud-hosting, because although you have an actual HTTP server (usually Apache or Nginx) that you can't configure it much because it's managed by the provider, thus it gives you the same features (and limitations) as an a proper cloud-hosted static site solution (such as Netlify); and between self-hosting because of the same reasons, having an actual full-blown HTTP server, but one you can't fully control, thus it gives you fewer features than a self-managed VM in a cloud provider or self-hosted machine. Thus unless you need PHP, or `htaccess`, I think the other two alternatives make a better choice.

    The issue with "static sites", due to the de-facto requirements in 2022 imposed by the the internet "gatekeepers" (mainly search engines), is that they aren't "just a bunch of files on disk that we can just serve with proper `Content-Type`, `Last-Modified` or `ETag`, and perhaps compressed"; we now need (in order to meet the latest hoops the gatekeepers want us to jump through) to also do a bunch of things that aren't quite possible (or certainly not easily) with current web servers. For example:

    * minification (which I've cited in my article) -- besides compression, one should also employ HTML / CSS / JS and other asset minification; none of the classical web servers support this; there is something like <https://www.modpagespeed.com/>, but it's far from straightforward to deploy (let alone on a shared web-host;)

    * when it comes to headers (be it the ones for CSP and other security related ones) or even `Link` headers for preloading, these aren't easy to configure, especially if you need those `Link` headers only for some HTML pages and not all resources; in this regard I don't know how many shared webhosts actually allow you to tinker with these;

    The point I was trying to make is that if you want to deploy a professional (as in performant) static web site, just throwing some files in a folder and pointing Apache or Nginx at them isn't enough. If the performance you are getting by default from such a setup is enough for you, then perfect! If not there is a lot of pain getting everything to work properly.

  • quic

    quiwi 🥝 - QUIC implementation in Go.

  • webtransport-go

    WebTransport implementation based on quic-go (https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/)

  • fileless-xec

    Stealth dropper executing remote binaries without dropping them on disk .(HTTP3 support, ICMP support, invisible tracks, cross-platform,...)

  • yomo-wasmedge-tensorflow

    This application demonstrates how to launch high-performance "serverless" functions from the YoMo framework to process streaming data. The functions are embedded in a WebAssembly VM, WasmEdge, for safety, security, portability, and manageability.

  • diet256

    Coordinated INET256 Network Using QUIC

    Project mention: Ask HN: What Are You Working on This Year? | news.ycombinator.com | 2023-01-02

    I'm working on INET256, an API for secure identity based networking. The reference implementation, mesh256 is a mesh network using a distributed routing algorithm. There is also diet256, which is a centrally coordinated network with direct connections using QUIC over The Internet.



NOTE: The open source projects on this list are ordered by number of github stars. The number of mentions indicates repo mentiontions in the last 12 Months or since we started tracking (Dec 2020). The latest post mention was on 2023-05-21.

Go Quic related posts


What are some of the best open-source Quic projects in Go? This list will help you:

Project Stars
1 gost 12,818
2 quic-go 8,237
3 hysteria 5,596
4 algernon 2,239
5 yomo 1,449
6 gost 1,377
7 quicssh 576
8 kawipiko 358
9 quic 252
10 webtransport-go 165
11 fileless-xec 144
12 yomo-wasmedge-tensorflow 49
13 diet256 8
Access the most powerful time series database as a service
Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.