Best match

Most recent

Digital Ocean is a public cloud provider who focuses their services on simplicity and ease of scale for developers. Headquartered in New York (so close to me!), Digital Ocean has a complete ...

Make Waves to your Cloud Backup Strategy with Zerto LTR & DigitalOcean Spaces

LinkedIn

Zerto & Filebase – Cloud Backup to Decentralized Storage Network(s): IPFS, Storj, Sia, and Skynet! Jul 19, 2022 Zerto & Storj – Blockchain-Based Cloud Backup

Perform Instant File-level Restores using Zerto & Alibaba Cloud OSS

Get the most recent info and news about Filebase on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Filebase is the world’s first object storage platform powered by decentralized networks. We unify multiple networks under a single S3-compatible API to make decentralized storage accessible and easy to use. Our edge caching technology achieves industry-leading performance when writing and fetching data to and from decentralized networks, making them a highly-secure, geo-redundant alternative to traditional cloud storage at a fraction of the costs.

Filebase

Decentralized storage offers a different way of thinking about how to store and access your information. In this model, data is distributed across nodes that are geographically distributed and connected through a peer-to-peer network. This is very different from a traditional cloud model where data is siloed into regions that are prone to outages, and failure. By contrast, peer-to-peer networks are resilient to catastrophic events such as natural disasters, fires, or infrastructure compromise. is the world’s first object storage platform powered by decentralized storage networks, unifying multiple networks under a single S3-compatible API to make decentralized storage accessible and easy to use. Its proprietary edge-caching technology achieves industry-leading performance when writing and fetching data to and from Web3, making it a highly-secure, geo-redundant alternative to traditional cloud storage at a fraction of the costs. Filebase The Story of Filebase CEO Joshua Noble and COO Zac Cohen both come from backgrounds in the cloud computing world. In their careers, they had been exposed to AWS and the cost of centralized cloud storage, despite the weaknesses that the centralized cloud faces, such as security holes and crippling outages. In 2019, they co-founded Filebase with the vision of unifying multiple networks under a single S3-compatible API to make decentralized storage simple, accessible, and as easy to use as Amazon. By building a bridge that makes it possible for anyone to leverage the unique qualities of decentralized networks, Filebase is an easy on-ramp (Layer-2) for users of all skill levels and knowledge backgrounds to be able to utilize and build with blockchain-based solutions. Filebase has put in years of steady work to simplify all of the complexities of blockchains and cryptocurrency to make an object storage platform that is as familiar as Amazon S3, but with a completely different type of backend architecture. It manages all aspects of the data storage layer on behalf of its users such as minimum file or sector sizes, data retention issues, or requiring special software, skill sets and tokens required to utilize decentralized networks. IPFS Pinning Services Within the IPFS ecosystem, there are a variety of public gateways available for uploading files, but due to the IPFS garbage collection process, unless a file is explicitly pinned it will be removed the next time the garbage collection process runs. To solve this problem, numerous pinning services have emerged. Bridging the Gaps Filebase spent a lot of time researching and analyzing these other pinning services. Since its flagship S3-compatible API has processed over 1 billion files through the platform, the project started engineering work around how to offer a dramatically different type of IPFS pinning service. Here is what it found: Most IPFS pinning providers use Amazon S3 and other Web2 centralized object storage services under the hood. The "data store" of an IPFS server can be pointed to S3 using a simple plugin. Because AWS S3 is being used, providers are charging upwards of ~$150 per TB. If AWS goes down, IPFS servers go down too. Unless the data has been cached somewhere, user’s IPFS CID links are no longer accessible. Building Web3 with Web3 - IPFS Implementation Filebase is excited to share that it now supports IPFS with a proprietary feature that makes its IPFS pinning service unique. Files that are pinned onto IPFS using Filebase are actually being stored on Sia, one of the leading decentralized storage networks. This creates an environment where the data storage layer for Filebase IPFS nodes is highly available, and most importantly, geo-redundant by default. A Filebase edge location could suffer a complete outage, and other locations will simply pick up the slack. This is made possible because the underlying data storage layer is decentralized. There's a massive cost benefit too; this is available to all Filebase users for $5.99 per TB while the integration remains in the beta stage. This is a significantly reduced cost compared to other pinning services today, charging ~$100-$150 per TB. What’s Next for Filebase Filebase has a variety of upcoming developments and features planned, including: Bucket level access keys: Users will be able to create a pair of access keys specific to individual buckets, in addition to their account’s root level access key pair that can access all buckets on the account. Folder level IPFS CIDs: Users will be able to upload folders on IPFS and reference objects in those folders using the IPFS CID of the folder and the object’s key. Learn More at no cost, or check out the for a variety of tool configuration guides, code development documentation, and deep dives on different Web3 topics such as Geo-redundancy and NFTs. Sign up in-seconds Filebase documentation If you want 5TB of additional storage for one-month at no expense - Upgrade and use code “IPFS” For questions, find them on Twitter , send Filebase an email at hello@filebase.com, or join their community . @Filebase Discord server Stay informed on IPFS Sign up for the IPFS Weekly newsletter ( ) for the latest on releases, upcoming developments, community events, and more. example Zac Cohen 14 April, 2022 Please send me the newsletter Blog & news Press Code of conduct Security Github YouTube Twitter LinkedIn © | Except as , content licensed | | | Protocol Labs Protocol Labs noted CC-BY 3.0 Terms Privacy DMCA

Filebase: Building Web3 with Web3

Filebase is excited to announce the launch of the Filebase + Akash Hackathon, a 7-week online event kicking off on September 1st that offers developers and teams the opportunity to build applications that integrate Filebase + Akash and win $10,000 of AKT and up to $250 in free object storage. About Filebase Filebase is the world’s first S3-compatible object storage platform that allows you to store data in a secure, redundant, and performant manner across multiple decentralized storage networks. Additionally, Filebase’s proprietary edge caching technology helps customers achieve industry-leading performance when fetching data from decentralized networks. About Akash Akash Network, the world’s first decentralized and open-source cloud, accelerates deployment, scale, efficiency, and price performance for high-growth industries like blockchain and machine learning/AI. Developers leveraging Akash Network can access cloud computing at up to three times less than the cost of centralized cloud providers like Amazon Web Services, Google Cloud, and Microsoft Azure. Hackathon Key Dates Hackathon kick-off September 1: Hackathon Office Hours via Twitter Spaces with the Akash + Filebase teams ( ) September 14: Set a reminder Hackathon ends October 20 23:59 PST: Judging period begins October 21: Judging period ends October 29: Hackathon winners announced October 30: Prizes 🏆 1st place prize $10,000 AKT + up to $250 in free object storage credits on Filebase 🥈 2nd place prize: up to $150 in free object storage credits on Filebase 🥉 3rd place prize: up to $100 in free object storage credits on Filebase Judging Criteria How will this project impact the growth of the Filebase and Akash ecosystems? Potential Impact: How well does the project work? Functionality: How unique is the project idea and execution? Novelty: Is the user experience and design of the project well thought out? Design: Is the project beginning to market and garner interest from the community? Go-to-market Strategy: Example Use Cases We want to see a user-friendly functional app that a dev can run and use for deploying and managing projects. Also, ideally, this app or tool will be run and maintained 24/7. Building Fully Decentralized Webapps Persistent Storage for Decentralized and P2P Apps Off-Chain Storage for Blockchains Censorship-resistant Website Hosting Server-side Scraping, Backup & Data Publishing Run a headless CMS on Akash, and front-end and asset storage on Filebase. Rails App Framework NodeJS App Framework Wordpress as a service on Akash Ghost CMS on Akash Integrate Filebase + + Akash Supabase Integrate Filebase + + Akash Planetscale Example Projects Fastify Deploy to Filebase and Akash Unstoppable Web 2.0 - Akash Guidebook PostgreSQL restore/backup (Pinterest clone) - Ruby on Rails with Sia (on Filebase) and Auth0 Awesome Apps on Akash Registration Process 1. Register for a free 5GB storage account with Filebase 2. To upgrade and receive 1TB of free object storage for 2 months, use code HACKATHON 3. Register for the Akash Filebase Contest on Gitcoin 4. Introduce yourself and your idea with a post on the Akash Filebase Contest Forum 5. Add your Akash address in to receive $100 in initial funding for your idea. your profile 6. Join the Discord server and send a hello world! in the #filebase channel. http://discord.Akash.network Submission Process 1. by October 20th to be reviewed by the community, Akash team, and Filebase team. Submit a detailed post publicly on the forum 2. By October 30, the winners will be announced. What to Submit Project name and a list of team members A description of what your product does and why you decided to build it Demo video or presentation slides. Your video should be around 3 minutes long and include a demo of your working project. Videos must be made publicly visible. Access to your working application or Github code repository. Access must be provided the working application or code for judging and testing by providing a link to the website, functioning demo, or a Github repository Complete submission form Resources Learn more about Filebase Follow Filebase on social

Win $10k AKT in the Filebase + Akash Hackathon

Blockchain storage is appearing rapidly across the market. With a few companies doing intensive R&D in this space to offer a more secure, cheaper and responsive offering. is built on the . Their solution is enabled by Blockchain technology which enforces cryptographic governance to ensure that files are stored in a safe, secure and available manner. Filebase Sia decentralized network Once data is uploaded to Filebase, it’s stored on the Sia network. By doing so your objects get sharded into 30 pieces using Reed-Solomon erasure coding. To ensure security, these pieces are encrypted and distributed to servers scattered throughout the world for maximum redundancy. To offer incredible availability, only 10 of the 30 pieces are ever needed to recover a file. A great way to mitigate downtime without paying for additional infrastructure. Compared to AWS S3, Filebase’s offering is completely S3 compatible which comes with their S3-Compatible API, enabling you to build into the storage without paying for API requests, or egress costs. Overall, due to not needing to pay for additional infrastructure and overhead, Filebase extends to their customers no bandwidth charges for egress or API request fees – their $15 / mo for 3TB of data is very appealing as you know what you are paying for and don’t have any abrupt hidden service costs. Add virtual file system fabric to the mix, you can now spin Filebase into a decentralized and secure . Couchdrop’s SFTP server, SMB/NFS share or a file-sharing platform If migrating, replicating or backing up to Filebase is your cup of tea, the is happy to help do the work in this space. or move directly to affordable blockchain decentralized storage from a traditional on-premise server using SMB/CIFS, NFS or SFTP. Movebot Migrate from S3, Dropbox or another cloud endpoint Previously published at https://movebot.io/blog/blockchain-s3-storage-with-filebase

How To Create Blockchain S3 Storage with Filebase

Have you ever been visiting your grandparents or other family members, and they ask you a question that starts off, “Well you know about tech, right? Can you explain this concept to me? I saw it on the news the other morning,” or something along those lines? Sometimes, what they’re asking about can be as simple as what new colors the iPhone comes in this year or what Samsung’s newest phone looks like, and why it folds in half. Other times, these concepts are more technical in nature, like what an NFT is or how data breaches happen. Determining how to explain these concepts to your family members that are nontechnical can be challenging, and sometimes even when you break it down to the simplest of terms, it’s still not a concept that they can wrap their heads around. So what should you say if someone asks you about what decentralized storage is and why it’s important? How should you explain this concept to someone like your grandma in a way that she’ll understand what you’re talking about? Blockchains First, let’s explain how blockchain networks operate. Decentralized storage networks are created using blockchains. A blockchain is a network that uses peer-to-peer technology to connect resources. To your grandma, a peer-to-peer network is like when she phones one of her friends to coordinate their weekly brunch meeting. That phone call is an example of a peer-to-peer network connection. It’s a direct connection used to share information between two entities. On a blockchain, each peer is referred to as a node. This node can be a home computer, like your grandma’s Windows 7 computer that she uses to log onto Facebook once a week, or it can be a high-performance computing server located in a data center. To be added to the blockchain, special software gets downloaded onto the node for it to connect to the blockchain. To your grandma, she and her friends are nodes in their peer-to-peer network. Every node provides its local resources, such as processing power and empty storage capacity, to provide resources to the blockchain to be used for storage and other blockchain transactions. This is like when your grandma goes to brunch with her friends, and they split the bill. Each entity contributes its resources to the network. Decentralized Storage So now that we know how a blockchain network operates, the best way to explain how decentralized storage works is to think about how your grandma is used to storing files. Say your grandma has a file cabinet with multiple drawers. Inside each drawer are manilla file folders, each with one file in them. Each individual file could be stored in one folder together, but instead, your grandma has kept them each in their own folder to organize things. When you store a file on a decentralized storage network, the file gets broken apart into a number of different pieces. This process is called erasure coding. Each piece is then individually encrypted with a special algorithm. To your grandma, this is like when she stores her files each in their own manila folder, then places each folder in different file cabinet drawers, with each drawer having its own lock. Next, each piece of the file stored on the decentralized storage network is stored across the world in a wide variety of locations. No file can be accessed without the minimum number of other pieces, which only you can access due to that special algorithm that gets applied during the erasure coding process, so there's no concern about the owner of the node that stores a piece of the file being able to access the file. This is like if your grandma had multiple filing cabinets across her house. One file in one folder would get stored in the first filing cabinet in the top drawer, and another file in another folder would get stored in the second filing cabinet in the bottom drawer. Everything could be stored in one folder, in one drawer, in one filing cabinet, but instead, they get split apart and stored separately. To access the entire set of files, each file must be retrieved from each drawer in each filing cabinet. Each drawer is locked with its own unique key, and only your grandma has the keys to be able to open the drawers. When the file is broken apart into multiple pieces and erasure-coded, not all of those pieces are required to reassemble the file to be accessed or downloaded. This is a feature that’s in place specifically to ensure data integrity. ⅔ of the file chunks can be offline, corrupt, or otherwise inaccessible, but you can still access your file. You won’t even know that there are offline or corrupt chunks, it won’t change how you access your file at all. This is like your grandma having multiple copies of different files. She might have 3 copies of one file, with each copy stored in its own folder, then stored across three different filing cabinets in three different drawers. For this file, she only needs one copy to access the contents, so she doesn’t need to access all 3 copies of it to use the file. So if she loses the key to one of the drawers and has to wait for a locksmith, she can open another filing cabinet and go to another drawer that has one of the copies of that file. It’s the same concept with decentralized storage - if one file chunk can’t be accessed, the file can still be accessed and downloaded with no interruption, they just use a chunk stored in another location to piece together the file. Why Would You Use Decentralized Storage Instead of Centralized Storage? After all this explaining, your grandma might wonder - why should you use decentralized storage? One of the biggest advantages is the innate security that comes with decentralized storage. Since each file is erasure coded, encrypted, and stored across the globe, and you need at least ⅓ of the pieces to access the file, files are secure not only in integrity and accessibility but also in data privacy. No one can access the data file’s chunks besides the user who uploaded them. To your grandma, this is like when she stores a file in a file folder in one file cabinet drawer, locks the door, then goes down the hall and stores another file in a different file cabinet. She is the only one who has the keys to either file cabinet, so she is the only one who can access and retrieve the files. Another advantage of decentralized storage is reliability. Since decentralized storage is just that, decentralized, it has no single point of failure that would take the network down and make the data inaccessible. This means there are no more crippling outages that disrupt workflows or result in a loss of business. So now, you might have some ideas on how to explain decentralized cloud storage to your grandma, or any other family member that may ask! Questions? Check out our excellent documentation , or simply reach out to us: or by . found here hello@filebase.com joining by our Discord Experience Filebase today: Get started with 5GB of free object storage with no expirations and no trials.Experience Filebase today: Get started with 5GB of free object storage with no expirations and no trials. Experience Filebase today: Get started with 5GB of free object storage with no expirations and no trials.

Explaining Decentralized Storage to Your Grandma

Over the past two years, the NFT boom has taken the world by storm. Minting NFTs across various blockchains is now commonplace in the crypto world. However, the storage of these NFT assets is . IPFS, known as the , has become the common standard used to store NFT assets. often overlooked InterPlanetary File System One often overlooked detail is that IPFS is not a storage network in and of itself. It is much more of a data routing and transmission protocol. The IPFS network is a collection of nodes exchanging information. File entries can be "pinned" to the public IPFS DHT (distributed hash table) to let other nodes on the network know which hosts are storing which files. Within the IPFS ecosystem, there are a number of public gateways. Some of these gateways allow you to upload files, but there is often no guarantee that your file will remain online. Unless a file is explicitly pinned by an IPFS node, the file will simply be removed the next time the garbage collection process runs. This has surfaced a number of issues regarding the storage of NFTs. To help solve this problem, a few different pinning providers have emerged. For a fee, these providers will allow you to upload your files, and they will keep them actively pinned for you. However, this brings a new problem to light: where are these files actually being stored? Somewhere out there, an IPFS server is running and serving content, but where does the content ultimately live? Filling in the gaps We've spent a lot of time researching and analyzing this problem. Our flagship has processed close to 1 billion files and, just a couple of months ago, we put our thinking hats on to start working on this problem. S3 compatible API Here is what we found: Most IPFS pinning providers use Amazon S3 and other centralized object storage services under the hood. The "data store" of an IPFS server can be pointed to S3 using a simple plugin. Because AWS S3 is being used, providers are charging upwards of ~$150 per TB! However, if AWS S3 goes down, . Unless the data has been cached somewhere, your IPFS CID links are no longer accessible. This can result in an NFT "rug pull". your IPFS server goes down too A system with this configuration also has the net result of introducing a very fancy way to access AWS S3. If we are so reliant on AWS, why not use a simple HTTP URL instead? Why not build Web3 with Web3? We've come up with a solution to address the gaps listed above and we think it will benefit the entire crypto ecosystem. Simply put: Why not build Web3 with Web3? This creates an environment where the data storage layer for our IPFS nodes is highly available, and most importantly, geo-redundant. By using a decentralized network for storage, we are no longer reliant on a cloud provider's block storage volume (AWS EBS) or a centralized storage bucket. (AWS S3) All files that are pinned onto IPFS using Filebase are actually being stored on , one of the leading decentralized storage networks. Sia How do I pin data onto IPFS? Pinning data onto IPFS is easy. You have two options: Use our simple drag and drop interface within the Filebase dashboard Use our simple S3 compatible API When you upload a file, an IPFS CID (content identifier) will be returned. You can then use this CID to access your data from your own IPFS node, or any other IPFS gateway on the public internet. CID's are clearly displayed within our dashboard, and they can be retrieved programmatically as well. Once you've opened up an IPFS bucket from the dashboard, a CID column appears. You can click on any CID, and it will be automatically copied to your clipboard. The object overview page will also show you the CID, along with other details: If you're using the S3 compatible API, the CID will be returned in the response of a call. For example, if we run the following AWS CLI command: PutObject aws --endpoint https://s3.filebase.com s3 cp test-images/7FIMFhlMf6A.jpg s3://ipfs-test --debug The response is shown below. For convenience, we've highlighted the respective response header: We can also call the HeadObject API to fetch the CID at any time as well: aws --endpoint https://s3.filebase.com s3api head-object --bucket ipfs-test --key 7FIMFhlMf6A.jpg Now that IPFS functionality is live, we plan to continue building out this integration even further! Documentation , or simply reach out to us by . found here joining our Discord HackerNoon readers can and use code “IPFS” to get started quickly. Want 5TB free for one-month? sign-up

How to Pin Data onto IPFS to Create a Decentralized Storage Network

Mountain Duck is a free cloud storage browser application for Windows and Mac OSX that supports mounting cloud storage services on your local computer. By using Mountain Duck, you can mount Filebase, a decentralized cloud storage provider, as a drive on your local file system and use it just like a hard drive for file storage and management. Prerequisites To get started using Mountain Duck with Filebase, you will need to and install Mountain Duck. You will also need to have your Filebase and a Filebase to get started. download access and secret keys bucket Setting up Mountain Duck To set up Mountain Duck, start by opening the Mountain Duck client. From the top drop-down menu, select 'Amazon S3' from the list of options. Then, configure the following settings to connect to your Filebase account: Enter a nickname for the connection, enter the server URL as 's3.filebase.com', and set the port as 443. You will also need to provide your Filebase S3 API and S3 , found in the Filebase web console under . Access Key Secret Key Access Keys When you're finished setting the configuration details, select 'Connect'. Using Mountain Duck to Access Decentralized Cloud Storage A file explorer window will appear showing your Filebase buckets as mounted storage locations. You can now interact with your Filebase buckets like any other folder on your local computer. From this window, you can click and drag files and folders from other windows to be uploaded to your Filebase bucket. To confirm that the files are reflected in your Filebase bucket, check the bucket’s contents through the Filebase . web console It’s that simple! You can now continue to use your Filebase storage buckets on your local computer, making file backups seamless to the decentralized web. Experience the power of Web3 in seconds: Get started with 5GB of free object storage with no expirations and no trials. Need more storage?  Use code for 1TB of storage (your first month free) on us! "WEB3WELCOME"

Mounting Web3 Storage as a Folder on Your Desktop

You're chowing down at Thanksgiving dinner, talking about cloud storage, when your grandmother asks, "What the heck is object storage?” You freeze up. Your grandmother comes from a time when "storage" meant manila folders in a physical filing cabinet, and switchboards. You're not sure she's ever used her computer for anything other than Facebook and watching cat videos on YouTube. What do you actually tell her? Say you're in charge of an extensive collection of paintings. The size of the collection often varies, as you acquire new pieces and loan out older ones for museum displays. Your main goal: keep all of the paintings safe from the elements and stored in a climate-controlled environment. You need somewhere to store this collection, and you have a couple of different choices as to where to keep it. Let's start with the Cloud... You could build a warehouse and pay for the electricity and other maintenance fees. Pro: All of your paintings would all be nearby and easily accessible. Con: You'd have to pay for the warehouse's maintenance and utilities in full, all the time, regardless of how many paintings are stored at one time. And if you anticipate that your collection may grow beyond the confines of the warehouse, you'll have to build another one. Option A: You could rent space offsite to store the paintings. Say you've found a storage facility that charges per inch of shelf space! Option B: Your paintings are kept in a large warehouse with items belonging to many other people, but you only pay for the area you use. During the times when your collection shrinks, it takes up less shelf space and therefore costs less. When the collection grows, the cost goes up. But since you're not paying to maintain any infrastructure, it is still more cost-effective and efficient than building your own storage. This scenario illustrates the difference between on-premise and cloud storage. You can tell Grandma that a server is just a computer providing resources, like storage space, to thousands of computers. In the past, companies would house all of their digital data across servers in located they owned and operated. Cloud storage very similar to our shared storage facility in this scenario. There are numerous servers located offsite, where many people can store their data for a low cost. Their pricing model allows that you pay only for what you use, so you don't have to pay for any space you're not actively using. Let's break down cloud storage further into a couple of different categories: File and Object storage. Remember those documents that people used to store in manila folders in a filing cabinet? File storage is very similar to that. It's the type of storage that most people are familiar with today. Your files are named and stored in folders, which are sometimes nested within other folders. You find them by navigating to a "path" through the file structure. For instance, you may have a folder titled "Taxes." Within that folder, you might have sub-folders for each year's tax info, and within those folders, you may have your tax-related documents, e.g., your W-2, receipts, student loan documents, etc. So to find your 2019 W-2, you would open up the "Taxes" folder, pull the "2019" folder out, then find the W-2. which are often used with cloud storage, work a little bit differently. An object is similar to a file, but instead of locating it using nested folders, you utilize a unique ID. Objects, Imagine you have a variety of objects sitting on a shelf. There is no rhyme or reason to what objects are where. You have a water bottle, a book, a toy robot, a stuffed owl, and so on, all stored together on the shelf. They each have a unique ID that you can use to look them up when you need to locate a particular thing. So say you know your stuffed owl has an ID of 453. To find it, you go to space 453 on the shelf. Voilà - there's your stuffed owl. This is analogous to the difference between files and objects stored on a computer. are stored and retrieved using a nested folder system. They also have fixed metadata (data about data), e.g. the name of the file, its author, the date and time it was created, and the file size. The metadata cannot be customized. Files In contrast, are stored and retrieved using unique IDs, and they implement customizable metadata. So they might store different metadata depending on what type of object they are. objects Something like an X-Ray might include metadata related to the patient’s name, type of injury, the name of the attending doctor and X-Ray technician, etc. Meanwhile, a painting might have metadata like the artist’s name, the painting’s title, the name of the series it belongs to, its price, etc. So there you have it: cloud AND object storage in a nutshell. Now that you know, you can go to Thanksgiving dinner and educate your grandma (and grandpa!) in the intricacies of the cloud today. Check out our and our Object Storage service to learn more. Documentation on Filebase Experience Filebase today: Get started with 5GB of free object storage with no expirations and no trials.

Filebase

filebase.com

6 employees

Since 2019

COMPANY RANKING

Filebase

EVERGREEN INDEX #1793

See more notable links about Filebase

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Filebase

Filebase

Filebase

filebase.com

6 employees

Since 2019

COMPANY RANKING

Filebase

EVERGREEN INDEX #1793

Related CompaniesRank

Filebase Story MentionsComplete List

See more notable links about Filebase

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Filebase

Filebase