update book for typos
update branch to fit with main
This commit is contained in:
@@ -4,11 +4,11 @@ sidebar_position: 20
|
||||
---
|
||||
|
||||
|
||||
# Government, Commercial hosters, Telco and Enterprise Roadmap
|
||||
# Government, Commercial Hosters, Telco and Enterprise Roadmap
|
||||
|
||||
We are working on our Government, Commercial hosters, Telco and Enterprise Release of our Technology.
|
||||
We are working on the government, commercial hosters, telco and enterprise releases of our technology.
|
||||
|
||||
> 90% of the work has been done as part of our base offering but we need additional features for enterprise
|
||||
> 90% of the work has been done as part of our base offering but we need additional features for enterprises.
|
||||
|
||||
## Enterprise User Interface
|
||||
|
||||
@@ -22,7 +22,7 @@ The current user interface is designed for an open-source tech audience. For ent
|
||||
|
||||
## Windows Support
|
||||
|
||||
The virtual Machine technology we use does support windows, but we need to do some further integration.
|
||||
The virtual Machine technology we use does support Windows, but we need to do some further integration.
|
||||
|
||||
## High Performance Network Integration
|
||||
|
||||
@@ -40,14 +40,16 @@ Next to the existing already integrated storage backends we want to support a hi
|
||||
- Supports our high speed backbone as defined above
|
||||
- Scalable to thousands of machines per cluster.
|
||||
- Replication capability between zones.
|
||||
- **Custom Integration**: We offer integration with selected storage equipment from our customers, accommodating custom integration requirements.
|
||||
- Custom Integration
|
||||
- We offer integration with selected storage equipment from our customers, accommodating custom integration requirements.
|
||||
|
||||
## Service Level Management
|
||||
|
||||
- The system will have hooks and visualization for achievement of Service levels.
|
||||
- This will allow a commercial service provider to get to higher revenue and better uptime management.
|
||||
|
||||
## Support for Liquid Cooling tanks
|
||||
## Support for Liquid Cooling Tanks
|
||||
|
||||
- Do a test setup in liquid cooling rack or node, we can use our selfhealing capabilities to manage better.
|
||||
- Is Integration effort, not really code changes
|
||||
- Do a test setup in liquid cooling rack or node.
|
||||
- We can use our self-healing capabilities to manage in a better way.
|
||||
- This is an integration effort, and not much code changes are needed.
|
@@ -5,25 +5,27 @@ hide_title: true
|
||||
---
|
||||
|
||||
|
||||
## Our private AI agent called Hero, High Level Roadmap
|
||||
## AI Agent High Level Roadmap
|
||||
|
||||
Hero is our private AI agent.
|
||||
|
||||
The first version of our Hero enables the management of core services such as an innovative database backend, a sovereign decentralized git system, and the automatic integration and deployment of our workloads.
|
||||
|
||||
This stack allows everyone to deploy scalable web 2/3/4 apps on top of the TFGrid in a full automated way.
|
||||
This stack allows everyone to deploy scalable Web 2,3 and 4 apps on top of the TFGrid in a fully automated way.
|
||||
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------ |
|
||||
| Hero Publisher | Publish websites, e-books, ... on top of TFGrid | Q2 25 |
|
||||
| Hero CI = Continuous Integration | Easier to use Continuous Integration / Development, very powerfull, with multi node support | Q2 25 |
|
||||
| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in hero Publisher | Q2 25 |
|
||||
| Hero Publisher | Publish websites, e-books, and more on top of the ThreeFold Grid | Q2 25 |
|
||||
| Hero CI = Continuous Integration | Easier to use Continuous Integration/Development, very powerfull, with multinode support | Q2 25 |
|
||||
| Hero Play | Integrate declarative automation and configuration management as part of wiki approach in Hero Publisher | Q2 25 |
|
||||
| Hero Git | Alternative to centralized Github (based on Gitea), fully integrated on top of TFGrid | Q2 25 |
|
||||
| Hero DB | Flexible ultra redundant database stor with indexing, queries, stored procesudes, super scalable replication | Q2 25 |
|
||||
| Hero OSIS | Object Storage and Index system integrates with hero Git, all data on git based backend | Q2 25 |
|
||||
| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names. | Q2 25 |
|
||||
| Hero OSIS | Object Storage and Index system integrates with Hero Git, all data on git based backend | Q2 25 |
|
||||
| Hero WEB | Web framework (with co-routines) using Vlang, deployable globally on TFGrid, integrated with Mycelium Net and Names | Q2 25 |
|
||||
| Hero Monitor | Monitor all your different components on redundant monitoring stack | Q2 25 |
|
||||
| Hero Happs | Hero natively supports Holochain HAPPS | Q3 25 |
|
||||
| Hero Actors | Hero can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps. | Q3 25 |
|
||||
| Hero Web 3 Gateway | Hero aims to have native support for chosen Web3 partner solutions (dfinity, bitcoin, eth, ...) | Q3 25 |
|
||||
| Hero Actors | Hero can serve actors which respond and act on OpenRPC calls ideal as backend for web or other apps | Q3 25 |
|
||||
| Hero Web 3 Gateway | Hero aims to have native support for chosen Web3 partner solutions (Dfinity, Bitcoin, Ethereum, and more) | Q3 25 |
|
||||
|
||||
All of above is fully integrated with Mycelium Network and the TF Grid.
|
||||
All of the specs above are fully integrated with the Mycelium network and the ThreeFold Grid.
|
||||
|
@@ -8,36 +8,39 @@ sidebar_position: 2
|
||||
|
||||
# Roadmap in Phases
|
||||
|
||||
## phase 1: wave 1 of companies, leading to our expertise (DONE)
|
||||
## Phase 1: Wave 1 of Companies, Leading to Our expertise (DONE)
|
||||
|
||||
- technology creation, was result of 20 years of evolution
|
||||
- Technology creation
|
||||
- This was result of 20 years of evolution
|
||||
- 7 startups acquired as part of this process
|
||||
- technology used globally by big vendors
|
||||
- +600m USD Exits
|
||||
- Technology used globally by big vendors
|
||||
- +600m USD in exits
|
||||
|
||||
## phase 2: proof of tech (DONE)
|
||||
## Phase 2: Proof of Tech (DONE)
|
||||
|
||||
- Technology launched globally (as opensource)
|
||||
- +60,000,000 vcpu active
|
||||
- Open source technology launched globally
|
||||
- +60,000,000 active vCPU
|
||||
- Large scale proof of core technology
|
||||
- Focus on early adoptors in tech space (cloud, web 2/3 ...)
|
||||
- Focus on early adoptors in tech space (Cloud, Web2, Web3, etc.)
|
||||
- 50m USD funded by founders, community and farmers (people providing capacity)
|
||||
|
||||
## phase 3: commercialization & global expansion (START)
|
||||
## Phase 3: Commercialization & Global Expansion (START)
|
||||
|
||||
### phase 3.1: Commercial Partners
|
||||
### Phase 3.1: Commercial Partners
|
||||
|
||||
- ThreeFold Launches with Commercial Strategic Partners
|
||||
- ThreeFold Launches with commercial strategic partners
|
||||
- Telco Operatators
|
||||
- IT Integrators
|
||||
- Enterprise Roadmap delivered < 6 months (is mainly integration, documentation and UI work)
|
||||
- Together with partners we deliver on the many projects which are in our funnel today e.g. East Africa, Brazil
|
||||
- Enterprise roadmap delivered within 6 months
|
||||
- This is mainly about integration, documentation and UI work
|
||||
- Together with partners we deliver on the many projects which are in our funnel today, e.g., East Africa, Brazil
|
||||
|
||||
### phase 3.2: Large Scale Financancing for Infrastructure
|
||||
### Phase 3.2: Large Scale Financancing for Infrastructure
|
||||
|
||||
**Large scaling financing round**
|
||||
**Large Scaling Financing Round**
|
||||
|
||||
- financing for infrastructure projects (trillions available right now for infra in emerging countries)
|
||||
- Public STO (security token offering), let world co-own the infra for their Internet
|
||||
- large partnerships drive alternative to Tier 3/4 Datacenters
|
||||
- Financing for infrastructure projects (trillions available right now for infrastructures in emerging countries)
|
||||
- Public STO (security token offering)
|
||||
- This lets people around the world to co-own the infrastructure for their internet
|
||||
- Large partnerships drive alternative to Tier 3 and 4 datacenters
|
||||
|
||||
|
@@ -5,13 +5,13 @@ hide_title: true
|
||||
---
|
||||
|
||||
|
||||
## Version 3 Proof of Concept Network Life
|
||||
## Our Proof of Concept Network is Live
|
||||
|
||||

|
||||
|
||||
Every day people expand the ThreeFold current Network (Grid) and deploy applications on it.
|
||||
Every day people expand the current ThreeFold V3 Grid, our decentralized proof of concept network, and deploy applications on it.
|
||||
|
||||
The current network is a proof of concept network which has shown that the concept and technology works, we are now going to the next step which is full blown commercialization.
|
||||
The current network has shown that the concept and technology work. We are now going to the next step which is full blown commercialization.
|
||||
|
||||

|
||||
|
||||
|
@@ -9,8 +9,7 @@ sidebar_position: 3
|
||||
### Status Today
|
||||
|
||||
The core offering is functioning effectively, maintained through a community-driven, best-effort approach. Currently,
|
||||
there are no Service Level Agreements (SLAs) in place, and there should be increased visibility for users regarding their expectations for uptime,
|
||||
performance, and other service related requirements.
|
||||
there are no Service Level Agreements (SLAs) in place, and there should be increased visibility for users regarding their expectations for uptime, performance, and other service related requirements.
|
||||
|
||||
The uptime and stability of Zero-OS are very good.
|
||||
|
||||
@@ -43,17 +42,17 @@ Below you can find some of the planned features of TFGrid 4.0 mainly to achieve
|
||||
|
||||
| | Roadmap | Timing |
|
||||
| ----------------------------------- | ---------------------------------------------------------------- | ------ |
|
||||
| Zero-OS v4 (our next major release) | v4, no more TFChain, mutual credit, marketplace | Q2/3 25 |
|
||||
| Zero-OS v4 (our next major release) | V4, without TFChain, mutual credit, marketplace | Q2/3 25 |
|
||||
| Zero-Images from Docker | CI/CD integration (See Hero CI/CD) | Q1 25 |
|
||||
| Zero-Images Hub Integration | CI/CD integration (See Hero CI/CD) no more need for separate Hub | Q1 25 |
|
||||
| Mycelium Core | Just more hardening and testing | Q1 25 |
|
||||
| Mycelium Message Bus | Replace our current RMB, all our own RPC over Mycelium | Q1 25 |
|
||||
| Unbreakable Storage UI | Integration in UI, better documentation | Q1 25 |
|
||||
| Unbreakable Filesystem UI | Integration in UI, better documentation | Q1 25 |
|
||||
| Zero-OS VM's Cloud Slices | Integration Hero CI , use cloud slices to manage | Q2 25 |
|
||||
| Zero-OS VM's Cloud Slices | Integration Hero CI, use cloud slices to manage | Q2 25 |
|
||||
| Zero-OS Monitoring Docu | More docu and easier API | Q2 25 |
|
||||
| Zero-OS Web Gateway Expansion | Need more deployed, better integration with new Mycelium | Q2 25 |
|
||||
| Mycelium Names | in v4, name services | Q3 25 |
|
||||
| Zero-OS Cloud,Storage,AI Slices | as part of marketplace for v4, flexible billing mutual credit | Q3 25 |
|
||||
| Mycelium Names | In V4, name services | Q3 25 |
|
||||
| Zero-OS Cloud,Storage,AI Slices | As part of marketplace for V4, flexible billing mutual credit | Q3 25 |
|
||||
| FungiStor | A revolutionary different way how to deliver content | Q3 25 |
|
||||
| Zero-Images on FungiStor | Can be stored on FungiStor | Q3 25 |
|
||||
|
Reference in New Issue
Block a user