Fivnex: Our Future

We recently gave a minimal version of the monetary stuff over on Discord. If you have read that, understand there is a LOT more information here too, and a lot more in detail without the 2K character limits. In this article, we wish to explain Fivnex's future, how things will run, and going into detail on what we want to do. We will also talk more about Fivnex as a business, how things will be reported, giving back to users, and more. 

Running Fivnex

At Fivnex, we want to be transparent as possible. Part of that includes drawing our needs, writing our wants, and painting the picture for a better future. The needs will include something non-Americans or non-business-owning Americans will refuse to acknowledge as a need. Incorporation.

One of our primary needs as an American startup is to incorporate. Fivnex will incorporate as an  LCC. The reasons we need to do this are simply that it makes taxes so much easier, we will have the proper documents we need to run Fivnex and not be leaning a little too close to the grey area as we are now. We will also trademark the name Fivnex as we have been having hints of issues with people. We don't feel like this is too much of a concern, but knowing the toxic sides of the community we are in is important.

We will incorporate through LegalZoom, and incorporating under the state of Colorado (where Fivnex's CEO is located, and where all of the onsite buildings will be). The current costs of incorporation, of which we really want to be done right and by professionals, will cost us $600+ in a one-time-payment and $250/year for the registered agent (Which as to not do our friends and or family, will NOT be one of us. A registered agent is required by law).

This part of the business is more or less managed and has a plan with a million backup plans. Let us remind you that Fivnex will not be profitable for the first few years of Fivnex's existence. This heads up is for those currently investing, or planning on investing, we are going, to be honest. Since things are chaotic, we cannot give all the fancy-schmancy graphs and data. This does not mean we won't do those, they will just be more hindsight than foresight. More on that later. 

For Fivnex to run properly, however, we must also talk about what we need. The first thing is structure. This is still an ongoing discussion inside of Fivnex, however, we do have short/medium-term solutions including the Fivnex Browser, an open-source tool built on electron to help us manage what sites we are using. It will literally be a point-and-click browser for Fivnex's most important jobs (like managing social media platforms, writing blog posts, managing the many crowdfunding sites we are utilizing, and cryptocurrency wallet management). The Fivnex Browser is not a fully usable product made by Fivnex, it is literally no more than links and tools for searching on the Ecosia search engine. It will also include a couple of other tricks, and also a bare-bones start page that is more Fivnex being able to access stuff that is easier to access and doesn't need a million management things to use it.

For structure, we already have what we need. We already can manage our domains quite well with Porkbun, Namecheap, and Cloudflare. We have 100% of our code on GitHub in organizations to make sure no one specific org gets too crowded. Having specialty organizations is important to running Fivnex. Using Fivnex as our product development line (Except Keter which is advanced to the point of needing its own organization to manage properly), FivnexWeb is where all the website code is. Fivnex Foundation is to manage the Fivnex Foundation who's work is FAR SEPERATED from Fivnex itself. We have the FivnexMediaInteractive organization for our upcoming games (including publishing for other smaller studios) as well as tools/scripts/assets to make making games more simple, we have the FivnexTools organization which has tools to help Fivnex function (including the mentioned start page and Fivnex Browser).

Another need for Fivnex is money. To put it simply, there is not much else we can do until products are released. This is because we have MORE THAN ENOUGH avenues for donations and a WIP option for cryptocurrency donations. You can find all this information at fivnex.co/support

Well, if that is what we need, what do we want? We really want Fivnex to have domains with all the top-level domain extensions. However, we are roughly happy where we are at. We also want to start releasing more small projects. Small things the community can enjoy and benefit from for 100% free but are low-cost and low-maintenance solutions. Stuff like LibQuicktime and LibOSSListing, and while these don't help Fivnex directly, it is something we want to do more of. These specific projects are the side of quantity over quality, where the idea is we find a problem in our development, build a library to help others, move on. The core of Fivnex's products is quality over quantity. We have only FOUR active products, one upcoming computer manufacturing division (built as a hopefully steady stream of income), and another product that is in project limbo.

While we are on the topic of projects, let's quickly explain how they work as they will be relatively important for the rest of the article. We have three classes of software, and while we would LOVE to use the names of the SCP categories, that is sadly 100% to the Keter project (owned by Fivnex) alone. These tiers are PRIM, CRUX, and MICRO.

PRIM is what we call products. It is the core of Fivnex, and the tools we spend a lot of time in branding and marketing into. These projects include Potabi, Keter, Wedeke, and MEML. Projects that are built to sell as part of the COSS model.

CRUX projects are lower-step projects that we don't sell like PRIMs. They will have high quality with fairly high quantity. These would be projects that are stuff like package managers, CSS frameworks (similar to that of Bulma and Bootstrap), web services, quick document editor, etc. These projects will have ZERO income through traditional means. Only donations. CRUX projects can also be killed by the community by one of these rules: Significant drop in users and donations (we will determine this project by project), by community votes and feedback, among others as we figure this out.

MICRO projects are medium-quality projects produced whenever we feel like there is demand for it. MICRO projects usually die and turn over to pure community support whenever. Since these are inexpensive to make, we do not care, and we would actually want to see what the community does with our dead MICRO projects. MICRO projects will also include experimental, non Fivnex ICU projects.

Public Relations and Investor Relations

Since Fivnex runs as a generic corporation, let's talk about how this will work. The first is public relations. Public Relations, in our eyes, is simply talking to our community and being transparent and honest. However, there will be different avenues. For early access to releases and blog posts, we will use Patreon and SubscribeStar. For early access of information and updates, all donation sources EXCEPT direct Bitcoin and Dogecoin (and other coin (not FIVCOIN, as that is cryptocurrency Patreon)) donations. Everything else will be available everywhere including blog, Twitter, Discord, etc. 

However, the interesting part is Investor Relations. Investor relations will, of course, be private. How that is managed will be investor newsletters. Investors will get a deeper dive into the insides of Fivnex through graphs charts, and able to ask more secretive parts about our business. While we will be 100% honest with finances, acquisitions, taxes, and more, there will be other parts not as public until it happens including large planned purchases, new office locations, and investor-only information.

Let's make something clear: we do not have any intention of being purely independent. As long as we have the majority of control over Fivnex and product and community management. As long as we stay open-source, the community continues to thrive, having the majority of control over product management, and having a way out of the acquisition, all will be fine.

Financial Transparency

Fivnex is about being honest. Here is how financial information will come out. Every quarter we will have three financial reports. The yearly continuous report, the beginning of each quarter (set to January 1st, April 1st, July 1st, and October 1st) dedicated to how each quarter will continue. On those same articles will be the third report, the actual quarterly report. There will also be a yearly overview which is just the completed Yearly Continous, which will have information on how much we paid in taxes, our income, our losses, our profits, our deficits, important dates and time, and more. While of course, it won't have EVERY LAST OUNCE of information, it will have everything important to mention.

Standardizing Fivnex

Fivnex is against standards and centralization. We are actively developing and conceptualizing licenses that allow for decentralization but that still gives returns to the original developer. These licenses are NOT complete, but you can see some of our earlier concepts in our Fivnex/License repo. Standards, "best practices", and centralization with software cause more harm than good in the vast majority of situations. Standards can work with stuff like programming language design, especially if you expect custom implementations. For example, MEML has standards so any implementation of MEML will be compatible with another version of MEML. The only place standards work is with compatibility between two platforms. That's why CPU architectures standardize, so even if stuff improves, software made on a Ryzen 3 works on an i7, or how HTML/CSS on Chrome browsers work the same on almost any modern browser (except a few edge cases, or early developments like with the browser in Serenity OS). However, most standards don't work. 

Some common issues are with standards that have no effect on compatibility. These include NPM, PIP, and Cargo. Cargo is the best working, but not using it is still a common thing, even if people don't recommend it as a "best practice", the general rule also applies to NPM and PIP. Unwritten standardizations are another problem. These kinds of standards aren't technically a thing but can still cause problems. FOR EXAMPLE, an unwritten standard for running a community is to have a Twitter/Facebook page. It's not something you HAVE to do, but it is a subconscious expectation. 

Now, will Fivnex have internal standards? Yes. Standards for licensing, product/project QC, versioning, contacting, working, etc. However, these standards make it easier for a Fivnex-specific workflow. 

Fivnex's Product Line

Fivnex has only a handful of products. Two 100% active (MEML and Potabi), Two in light development (Keter and Wedeke), and two in temporary or indefinite limbo (Fivnex Computers and CherryDE). Let's talk about these products and how we plan to profit off of them.

MEML is a very interesting case. Since HTML5 is our main competitor, getting profits on MEML will be difficult... however there are a couple things in mind. We will get to Wedeke later, but that will be one method of profit. Monetizing a markup language is not easy, but we have a couple of ideas. One way is for MEML to have paid early access to binaries, which give people who pay for early MEML access get support faster, and have the ability to test standards. Another idea is to sell first-party books on how to use MEML, how it works internally, and tips and tricks for new users. These books will have digital access and physical copies, under Creative Commons (Attribution, Share-alike, Non-commercial (so people can't resell the contents in the book)). We also plan on doing stuff like MEML project hosting (like GitHub Pages or Glitch.com for MEML). 

Potabi will actually use the power of DEFAULT OPTIONS to make money. Taking inspiration from both the Play Store and elementary OS's AppCenter, we plan to build an app store that has mobile supported apps only. Users will be able to toggle if they want open-source apps only, free apps only, or pay-what-you-want apps only. Developers will be allowed to charge for their apps if they so please, no matter what the app is licensed under. Our store will take a different approach to cuts of funds as well. For paid-only apps, it is a 20/80 split. 20% of the income goes back to us. For Pay-what-you-want apps (which always will be freely downloadable as well) will be 10/90 split. The reason for having the pay-what-you-want model being cheaper is to hopefully push more open-source developers to use that option to get paid for their software, while still supporting Fivnex. For 100% free apps, it is a 0/100 split, obviously. We will also not force any specific returns for say, running ads in an application. We will also allow third-party stores, even visible and downloadable in the Potabi store itself. The idea is that people get the freedoms they want, but the VAST majority of users will simply stick to what is defaulted on the system, a win-win.

Keter will follow all of the same steps MEML is doing, except Keter has two more things in mind similar to the GitHub Pages / Glitch.com system designed for MEML. First off is offering an AWS-like system for developers to run Keter programs for free. We will also have a premium Gitea-based Git hosting service designed to have features that even rival the abilities of GitHub or GitLab. For Keter, we also plan to have paid support, online virtual machines to test outputs of Keter applications (and only Keter applications). 

Wedeke is the interesting one. While Wedeke has to be 100% open-source, we have a couple ideas. Firstly we will utilize extensions and an extension store. These extensions can add practically anything to Wedeke. The best part? It will be built like Potabi's app store where there are paid-only extensions, pay-what-you-want extensions, and 100% free extensions, all with the same splits and rules (paid only 20/80 split, PWYW 10/90 split, Free no split). Wedeke will have an online IDE, similar to Glitch.com, but having paid feature extras like static site hosting, library management tools, project management, etc. Wedeke will also have professional editions that are open-source but on install asks for a license that when activated allows for extra features for people who either spent the time getting the binaries or compiling the source OR alternatively for those who pay for licenses (which also come with immediate support options).

CherryDE is in project limbo right now and might be completely discontinued in favor of another product in the future. No income information set. 

Fivnex Computers doesn't make software, but rather sells hardware. Other than income from the hardware itself, any OS developer can pay to have their OS as an option to buy with. Say risiOS (a Fivnex partner) wanted their OS on a Fivnex computer lineup. They can build and test it, then pay a small yearly fee, then BAM their OS is an option on Fivnex's hardware. While getting those alternative OS's as an option won't be immediate, it is available. How would developers be able to get their OS on our computers? We will require moderate testing, but as long as the OS can support AMD GPUs, AMD64/RISC-V/ARM CPUs, and known to work on similar machines to what we sell then it will be allowed. Optionally they can rent, buy, or borrow a Fivnex computer. Renting a computer means you can have it as long as you pay for it (monthly fees) and return it when you are done, and borrowing leaves a 3-month time scale to return the computer. How renting a Fivnex computer will work is they pay a monthly fee to keep the computer until the first of next month (or else they will be forced to send it back), and it is a set price. The computer has to be returned when done, with no exceptions (even if the costs of renting cover the cost of computers). There will also be damage fees (if products are damaged), Tinkering fees (if there was tinkering with the original hardware setup like testing with different drives or RAM sticks), and the final return fee which is a small fee that they pay upfront that includes shipping information, return packaging, final inspection costs, etc. 

How is Fivnex's Future Looking

Fivnex is looking extremely stable. While profits are not expected for the first couple of years in business, we can also survive without said profits. Fivnex, being well designed to function long-term with 0-income is a strong point. Fivnex is also designed to where if a product flops, recovery will be quick and simple. While we are having issues with keeping the community engaged at the moment, this issue is non-severe and has solutions planned. 

Fivnex's future is bright. We are looking for help. If you are interested in working closely with us, contact us at [email protected], or for professional inquiries [email protected]

Comments

Popular posts from this blog

ArisbluBSD: Why a new BSD?

ArisbluBSD: Why Linux is Slowly Corrupting Itself. 5 Reasons Why We Want to REPLACE Linux.

ArisbluBSD: What is to come?