Open Source Go File Sharing Software
Sort By:
Go File Sharing Software
View 303 business solutionsBrowse free open source Go File Sharing Software and projects below. Use the toggles on the left to filter open source Go File Sharing Software by OS, license, language, programming language, and project status.
-
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
Picsart Enterprise Background Removal API for Stunning eCommerce VisualsWith our Remove Background API tool, you can access the transformative capabilities of automation , which will allow you to turn any photo asset into compelling product imagery. With elevated visuals quality on your digital platforms, you can captivate your audience, and therefore achieve higher engagement and sales.
-
1
EdgeVPN
The immutable, decentralized, statically built p2p VPN
Fully Decentralized. Immutable. Portable. Easy to use Statically compiled VPN and a reverse proxy over p2p. EdgeVPN uses libp2p to build private decentralized networks that can be accessed via shared secrets. -
2
Cloud Torrent
Cloud Torrent, a self-hosted remote torrent client
Cloud torrent is a a self-hosted remote torrent client, written in Go (golang). You start torrents remotely, which are downloaded as sets of files on the local disk of the server, which are then retrievable or streamable via HTTP. Go is required to install from source. The provided set of core features requires large structural changes and therefore requires a complete rewrite for best results. This rewrite is in progress in the 0.9 branch though it will take quite some time. It will be capable of transfering files from and source file-system to any destination file-system. A torrent can be viewed a folder with files, just like your local disk, and Dropbox. As long as it has a concept of files and folders, it could potentially be a cloud-torrent file-system backend. During a file tranfer, one could apply different transforms against the byte stream for various effect. -
3
DefraDB
DefraDB is a Peer-to-Peer Edge Database
DefraDB is a Peer-to-Peer Edge Database. It's the core data storage system for the Source Network Ecosystem, built with IPFS/IPLD, LibP2P, CRDTs, and Semantic web3 properties. DefraDB is a user-centric database that prioritizes data ownership, personal privacy, and information security. Its data model, powered by the convergence of MerkleCRDTs and the content-addressability of IPLD, enables a multi-write-master architecture. It features DQL, a query language compatible with GraphQL but providing extra convenience. By leveraging peer-to-peer networking it can be deployed nimbly in novel topologies. Access control is determined by a relationship-based DSL, supporting document or field-level policies, secured by the SourceHub network. DefraDB is a core part of the Source technologies that enable new paradigms of decentralized data and access-control management, user-centric apps, data trustworthiness, and much more. -
4
transfer.sh
Easy and fast file sharing from the command-line
Easy and fast file sharing from the command-line. This code contains the server with everything you need to create your own instance. Transfer.sh currently supports the s3 (Amazon S3), gdrive (Google Drive), storj (Storj) providers, and local file system (local). For easy deployment, we've created a Docker container. For the usage with a AWS S3 Bucket, you just need to specify the following options, provider, aws-access-key, aws-secret-key, bucket, and s3-region. If you specify the s3-region, you don't need to set the endpoint URL since the correct endpoint will used automatically. To use a custom non-AWS S3 provider, you need to specify the endpoint as defined from your cloud provider. In preparation you need to create an access grant (or copy it from the uplink configuration) and a bucket. To get started, login to your account and go to the Access Grant Menu and start the Wizard on the upper right. -
Build Securely on AWS with Proven FrameworksMoving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
-
5
IPFS Kubo
An IPFS implementation in Go
Kubo was the first IPFS implementation and is the most widely used one today. Implementing the Interplanetary Filesystem - the Web3 standard for content-addressing, interoperable with HTTP. Thus powered by IPLD's data models and the libp2p for network communication. Kubo is written in Go. IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from previous systems such as Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single BitTorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built-in. You can also mount the world at /ipfs. -
6
Rain
BitTorrent client and library in Go
Rain is a fast, lightweight, and feature-rich BitTorrent client written in Go, designed to be used from the command line. It focuses on performance and simplicity, supporting both seeding and downloading operations with minimal system resource usage. Rain is ideal for automation, headless servers, and users who prefer terminal-based tools. It offers a clean API, making it easy to integrate into scripts and backend services that require torrent functionality. With its statically compiled binary and low dependency footprint, Rain can be easily deployed across different environments. -
7
Wayback
An archiving tool with an IM-style interface that prioritizes privacy
Wayback is a web archiving and playback tool that allows users to capture and preserve web content. It provides an IM-style interface for receiving and presenting archived web content, and a search and playback service for retrieving previously archived pages. Wayback is designed to be used by web archivists, researchers, and anyone who wants to preserve web content and access it in the future. Wayback is an open-source web archiving application written in Go. With a modular and customizable architecture, it is designed to be flexible and adaptable to various use cases and environments. It provides support for multiple storage backends and integration with other services. Whether you need to archive a single web page or a large collection of web sites, Wayback can help you capture and preserve web content for posterity. With an easy-to-use interface and powerful features, Wayback is a valuable tool for anyone interested in web archiving and preservation. -
8
go-libp2p-kad-dht
A Kademlia DHT implementation on go-libp2p
A Go implementation of libp2p Kademlia DHT specification. Client-side optimizations are described in optimizations.md. -
9
go-libp2p-pubsub-grpc
libp2p pubsub with controls exposed via a gRPC API
pubsubgrpc provides a LibP2P PubSub framework that can be used as a stand-alone gRPC pubsub server and API, or as a module/component of existing gRPC servers to provide LibP2P PubSub functionality. It uses proto3 and borrows some ideas from libp2p/go-libp2p-daemon and libp2p/go-libp2p-pubsub. -
Powering the best of the internet | FastlyEnsure your websites, applications and services can effortlessly handle the demands of your users with Fastly. Fastly’s portfolio is designed to be highly performant, personalized and secure while seamlessly scaling to support your growth.
-
10
ipfs-check
A tool for checking the accessibility of your data by IPFS peers
A tool for checking the accessibility of your data by IPFS peers. go build will build the server binary in your local directory. go install will build and install the server binary in your global Go binary directory (e.g. ~/go/bin) There are web assets in the web that interact with the Go HTTP server that can be deployed however you deploy web assets. Maybe just deploy it on IPFS and reference it with DNSLink. For anything other than local testing you're going to want to have a proxy to give you HTTPS support on the Go server. -
11
qrcp
Transfer files over wifi from your computer to your mobile device
qrcp binds a web server to the address of your Wi-Fi network interface on a random port and creates a handler for it. The default handler serves the content and exits the program when the transfer is complete. When used to receive files, qrcp serves an upload page and handles the transfer. Most QR apps can detect URLs in decoded text and act accordingly (i.e. open the decoded URL with the default browser), so when the QR code is scanned the content will begin downloading by the mobile browser. When sending multiple files at once, qrcp creates a zip archive of the files or folders you want to transfer, and deletes the zip archive once the transfer is complete. When receiving files, qrcp serves an “upload page” through which you can choose files from your mobile. The default configuration file is stored in $HOME/qrcp.json, however, you can specify the location of the config file by passing the --config flag. -
12
Pydio Cells
Formerly AjaXplorer, file sharing platform for the enterprise
Pydio Cells is the mature open source alternative to dropbox and box, for the enterprise. Why building your own box? You need to access your documents across multiple devices, and regularly share documents (weblinks) and folders with your contacts and teams. Still, using a consumer SaaS box or drive service is neither practical nor safe. And enterprise SaaS box or drive services are expensive and come with Disk Storage that you already have on your servers or private cloud. How to build your own box with Pydio? Easily install Pydio on your servers or cloud of choice, Simply share documents and folders with your teams, Administrate your box with an Entreprise grade console (rights, groups, plug ins), Access documents with a Web Gui, Smartphones and tablet apps (iOS, Android), Sync folders on your computer (PC, Mac, Linux). -
13
Simple-Http-File-Server
Simple http file server with Windows GUI application
This is a simple Windows GUI application that provides an http server service for sharing local files, and support upload file. It does not require installation and can be directly downloaded and run. -
14
Amplify
Automatic enrichment, enhancement, and explanation of your data
Amplify attaches afterburners to your data. Amplify explains metadata extraction, classification, tagging, and reporting. Eriches derivative data generation like thumbnails, previews, conversions, etc. Enhances batteries-included value-adds like data quality reports, image augmentation, OCR, translations, etc. Amplify leverages the decentralized compute provided by Bacalhau to magically enrich your data. A built-in suite of pipelines decides what your data is and how to best improve upon it. You can also self-host Amplify to trigger off your offline data sources and implement your own custom pipelines. -
15
Auspinner
Stateless CLI tool to easily pin CAR files to IPFS pinning services
auspinner is a stateless CLI tool to easily pin CAR files to IPFS pinning services. It's essentially a client for the IPFS Pinning Service API that speaks HTTP and Bitswap. -
16
C3 Go
Implementation of the C3 protocol in Go (WIP)
Go Implementation of the C3 protocol in Go (WIP). -
17
Cyber
Semantic non-deterministic Superintelligence consensus computer
Semantic non-deterministic Superintelligence consensus computer. A consensus computer allows for the computing of provable relevant answers without any opinionated blackbox intermediaries, such as Google, Amazon or Facebook. Stateless, content-addressable peer-to-peer communication networks, such as IPFS, and stateful consensus computers such as Ethereum, can provide part of the solution needed to obtain such answers. There are however at least 3 problems associated with the above-mentioned implementations. (1) the subjective nature of relevance, (2) difficulty in scaling consensus computers for over-sized knowledge graphs, (3) the lack of quality amongst such knowledge graphs. They are prone to various surface attacks, such as sybil attacks, and the selfish behavior of the interacting agents. In this document, we define a protocol framework for provable consensus computing of relevance, between content-addresable objects, which can be computed on GPUs. -
18
EdgeUR
Edge Gateway + Storage deal making using Delta
Edge is currently under heavy development. Dedicated light node to upload and retrieve their CIDs. To do this, we decoupled the upload and retrieval aspect from the Estuary API node so we can create a node that can live on the "edge" closer to the customer. Dedicated node assignment for each customer. The customer or user can now launch an edge node and use it for both uploading to Estuary and retrieval using the same API keys issued from Estuary. Switches the upload protocol. The user still needs to upload via HTTP but the edge node will transfer the file over to a delta node to make deals. -
19
Estuary
A custom IPFS/Filecoin node that makes it easy to pin IPFS content
A custom IPFS/Filecoin node that makes it easy to pin IPFS content and make Filecoin deals. We're excited to have you try out Estuary! Estuary is a reliable way to upload public data onto Filecoin and pin it to IPFS. As a developer, you have probably used API keys before. Estuary provides a unique identifier used to authenticate a user, developer, or calling program to an application programming interface we have created. If you don't know what an API key is, this tutorial will be challenging for you, but you can reach out to us if you're stuck. API keys are the standard way to authenticate a project with an API rather than a human user. It is also important you understand how to protect your API key/secrets from bad actors and abuse. If this concept is foreign to you, you might be better off just using https://estuary.tech and storing data through our website. -
20
FileDAG Storage
A distributed storage service built on the IPFS technology stack
FileDAG Storage A distributed storage service built on the IPFS technology stack. Different from the official implementation of IPFS, we focus more on data management, data reliability, availability and fault tolerance, and clustering of storage nodes. The minimum storage unit of FileDAG Storage is dag, which is the data block. Files or objects are organized in a merkle-dag structure, and multiple files or objects may share some data blocks. The obvious benefit of this is to reduce redundant data, especially for multi-version systems. Not only does reduce data redundancy, it also saves bandwidth on network transmissions. Every advantage has its disadvantage, the downside is that data management has become more complex. First, the file or object management module needs to be abstracted on the basis of merkle-dag; second, the file cannot be deleted directly, only the data blocks that are no longer needed can be released through garbage collection. -
21
Gilfoyle
Distributed video encoding, hosting and streaming
Gilfoyle is a web application from the Dreamvo project that runs a self-hosted media streaming server. Allowing you to easily implement media streaming in any application at any scale. It's written in Golang, mostly designed for Kubernetes and runs as a single Linux binary with PostgreSQL and RabbitMQ. -
22
Hydra Booster
A DHT Indexer node & Peer Router
A new type of DHT node designed to accelerate the Content Resolution & Content Providing on the IPFS Network. A (cute) Hydra with one belly full of records and many heads (Peer IDs) to tell other nodes about them, charged with rocket boosters to transport other nodes to their destination faster. Only run a hydra-booster on machines with public IP addresses. Having more DHT nodes behind NATs makes DHT queries in general slower, as connecting in generally takes longer and sometimes doesn't even work (resulting in a timeout). The total number of heads a single Hydra can have depends on the resources of the machine it's running on. To get the desired number of heads you may need to run multiple Hydras on multiple machines. -
23
Hyperledger FireFly
Hyperledger FireFly is the first open source Supernode
Hyperledger FireFly is the first open source Supernode: a complete stack for enterprises to build and scale secure Web3 applications. The FireFly API for digital assets, data flows, and blockchain transactions makes it radically faster to build production-ready apps on popular chains and protocols. Hyperledger FireFly has a pluggable microservices architecture. Everything is pluggable, from the Blockchain technology, token ERC standards, and custom smart contracts, all the way to the event distribution layer and private database. So if there aren't yet instructions for making FireFly a Supernode for your favorite blockchain technology - don't worry. There is almost certainly a straightforward path to plugging it in that will save you from re-building all the plumbing for your blockchain application from scratch. -
24
Hyprspace
A Lightweight VPN Built on top of IPFS + Libp2p
A Lightweight VPN Built on top of IPFS & Libp2p. Libp2p is a networking library created by Protocol Labs that allows nodes to discover each other using a Distributed Hash Table. Paired with NAT hole punching this allows Hyprspace to create a direct encrypted tunnel between two nodes even if they're both behind firewalls. Moreover! Each node doesn't even need to know the other's ip address prior to starting up the connection. This makes Hyprspace perfect for devices that frequently migrate between locations but still require a constant virtual ip address. -
25
IPDR
IPFS-backed Docker Registry
IPDR is a Docker Registry tool that proxies Docker registry requests to IPFS for pushing and pulling images. IPDR allows you to store Docker images on IPFS instead of a central registry like Docker Hub or Google Container Registry. Docker images are referenced by their IPFS hash instead of the repo tag names. IPDR is compatible with the Docker Registry HTTP API V2 Spec for pulling images.
