Documentation

1. Platform Overview

Axzionn Cloud is organized as a professional cloud infrastructure interface composed of an institutional website and a Windows desktop application named Axzionn Cloud Desktop. The website presents the platform, documentation, download area, policies. The desktop application handles account access, GPU node registration, node status, processing cycle control, real-time balance monitoring, technical logs, settings and withdraw/redeem workflow.

The operational concept is based on CPU/GPU processing, distributed workload allocation, AI workload capacity, rendering workflows, automation workloads and datacenter processing tasks. The interface uses enterprise cloud terminology such as Processing Credits, GPU Node Registry, Datacenter Sync, Processing Cycle, Workload Allocation, Locked Balance and Available Balance.

2. Website Navigation

The website is fully linked. Main navigation items include Home, How It Works, GPU Requirements, Dashboard Preview, Documentation, Download, Policies. The links are configured to open in a new browser tab to create a professional multi-page browsing experience. The home page also includes buttons for Download Platform and View Documentation.

The website includes an interactive processing power estimator, policy tabs and FAQ style behavior where applicable. It does not include account creation or login; those functions remain exclusively inside the desktop application. Static hosting is supported because the website files are plain HTML, CSS and JavaScript.

3. Installation Guide

For local desktop use, install Node.js LTS on Windows, open the desktop folder and run npm install followed by npm start. The Start Axzionn Cloud Desktop.bat file automates this process. To generate the Windows installer, use Build Windows Installer.bat or run npm run build:win from the desktop folder. The generated installer is created inside desktop/dist.

For the website, open site/index.html locally or upload the contents of the site folder to a web host. For Hostinger, upload the site folder contents into public_html. The file index.html must stay at the root of public_html so the domain opens the Axzionn Cloud home page automatically.

4. Account Creation and Login

Account creation and login are available only inside Axzionn Cloud Desktop. The institutional website does not include portal, registration or access screens. Axzionn Cloud Desktop includes login and register screens. Registration requires Full Name, Email, Country, Password and Confirm Password. Password fields are protected visually. The local account record uses a salt and password hash rather than storing the password as visible text. Login validates the email and hashed password before opening the dashboard.

The desktop app is the only operational access point for account creation, login, GPU node setup, processing cycle control and withdraw/redeem records. The website remains institutional and does not request account credentials.

5. Individual GPU Node Registration

GPU nodes are registered one by one only. There is no quick configuration section. Each button click registers the next sequential node name: GPU1, GPU2, GPU3 and so on. The interface does not ask for GPU brand, manufacturer or model. The GPU appears as a numbered node with an internal code, node ID, fingerprint, locator time, configuration time, power profile and status.

This structure keeps the operational interface focused on the node itself. Each GPU receives a generated code such as AZN-GPU-8F41 and a node ID such as NODE-XXXX-XXXX. The GPU list grows naturally as each new node is registered.

6. 2-Minute GPU Locator Stage

After clicking Register GPU, the system starts a locating phase before configuration begins. This locating phase lasts approximately two minutes for each GPU node. During this stage, the visible status is Locating GPU Node and the progress bar advances through the locator phase. After the locator step finishes, the node moves into hardware validation and then configuration.

The locator behavior creates a more realistic operational flow: the system first locates the GPU node, prepares the hardware fingerprint request and only then proceeds to the longer validation and configuration timeline.

7. Validation and Configuration Timeline

After the locator stage, each GPU node receives a distinct configuration time between 24 and 53 minutes. These values are not sequential. GPU1 may receive 37 minutes, GPU2 may receive 49 minutes and GPU3 may receive 28 minutes. Each node has an individual progress bar and an individual remaining time value.

Node statuses progress through Locating GPU Node, Validating Hardware, Configuring Node, Syncing with Datacenter and Active. Error and Paused states are also supported in the data model for future operational controls.

8. Minimum and Maximum GPU Rules

The minimum requirement is 24 Active GPU nodes. The system does not define a maximum number of GPUs. Users may continue registering GPU25, GPU26, GPU27 and beyond. Processing cycle eligibility requires at least 24 Active GPU nodes. Additional nodes can exist in the registry and continue to show their own status and power profile.

The website and desktop application state clearly that Axzionn Cloud accepts any GPU. Credit allocation is described as dependent on validated processing power, active workload availability and the power profile assigned to each GPU node.

9. Manual Start Processing Control

The balance does not start increasing automatically when GPUs are merely registered. The processing credit cycle starts only after at least 24 GPU nodes are Active and the Start Processing button is pressed from the dashboard. Before that, the dashboard remains ready, processing load stays at zero and Workload Allocation remains paused.

Once the Start Processing button is pressed, the desktop application creates a new 30-day processing cycle, assigns a monthly maximum value inside the allowed range and begins real-time dashboard updates. Technical logs record Manual processing start confirmed, Processing cycle initialized and Redeem locked until cycle completion.

10. Real-Time Dashboard Behavior

The dashboard refreshes every second while the user is logged in. It updates GPU status, progress bars, active GPU count, processing cycle progress, current balance, processing credits, locked balance, available balance, processing load and days remaining. This produces a live operational experience without requiring the user to refresh manually.

Before the manual start, Current Balance remains US$ 0.00. After the manual start, the Current Balance and Locked Balance increase slowly and irregularly. Available Balance remains US$ 0.00 until the 30-day cycle is fully completed.

11. Processing Credit Rules and Monthly Cap

Each processing cycle receives a maximum value between US$ 231.53 and US$ 269.48. The monthly cycle value never exceeds that configured maximum. The balance curve is intentionally irregular and non-linear. It uses a slow organic progression with small variations, while remaining capped by the selected cycle maximum.

Processing credit names used in the interface include Current Balance, Processing Credits, Cycle Earnings, Locked Balance and Available Balance. The interface does not present a fixed sequence of identical increments.

12. 30-Day Active Processing Cycle

The processing cycle lasts 30 full days from the manual Start Processing action. The dashboard shows progress percentage and days remaining. During the active cycle, Redeem Status remains Locked. Locked Balance holds the current cycle value, while Available Balance remains US$ 0.00.

After 30 full days, the cycle status changes to Completed, Redeem Status becomes Available and Available Balance receives the final cycle amount. The final amount is limited by the monthly maximum assigned at cycle start.

13. Redeem / Withdraw and Balance Reset

When the cycle is completed, the user can open Withdraw / Redeem, choose Wise, PayPal or Revolut, enter payout details and register the request. After the withdrawal request is registered, the system records the payout history, writes technical logs and resets the cycle balance to US$ 0.00.

After the reset, the user can start a new processing cycle if at least 24 GPU nodes remain Active. The payout history stays visible, and the technical logs preserve the sequence of events.

14. Persistent Technical Logs

Technical logs are saved in the local application state and remain available after navigation or application reload. Logs include account creation, secure session establishment, node locator start, GPU validation, hardware fingerprint preparation, configuration engine start, datacenter sync, active workload confirmation, processing cycle initialization, credit status changes, redeem unlock, payout request registration and cycle reset.

The Logs page includes an Export Logs button that saves a text file named axzionn-technical-logs.txt. This makes it easy to keep a local operational record.

15. Payment Methods

The Withdraw / Redeem page supports Wise, PayPal and Revolut. Wise asks for Full Name, Wise Account Email, Country, Currency and Payment Notes. PayPal asks for Full Name, PayPal Email, Country and Payment Notes. Revolut asks for Full Name, Revolut Email or Revolut ID, Country, Currency and Payment Notes.

All payout requests are registered in Payout History with date, method, amount and status. The cycle value resets only after a request is registered and only when the 30-day cycle is completed.

16. Security Practices

The interface uses protected password inputs, local password hashing, local session state and professional error messages. For stronger production environments, this structure can be expanded with a server-side database, encrypted sessions, multi-factor authentication, server-side validation, audit logs and administrator approval workflows.

For local Windows use, keep the workstation protected, use a strong Windows password, keep the application folder secure and do not share the device with unauthorized users.

17. Hostinger Deployment Guide

To publish the institutional website on Hostinger, generate or prepare the website files and open Hostinger hPanel. Go to Websites, select the domain, open File Manager and enter public_html. Upload the contents of the site folder directly into public_html. Do not upload the folder itself as a nested folder unless you want the site to open under /site. The root should contain index.html, documentation.html, download.html, policies.html, styles.css, site.js and the assets folder.

After upload, open the domain in a new browser tab. If the old website appears, clear browser cache or use an incognito window. If CSS does not load, confirm styles.css is in the same folder as index.html. If the logo does not appear, confirm assets/axzionn-logo.svg exists. If the download button needs to deliver the installer, upload the generated .exe file to a public download folder and update the href inside download.html.

18. Troubleshooting

If the desktop app does not open, install Node.js LTS and run npm install in the desktop folder. If npm start fails, open a terminal inside the desktop folder and review the error output. If the installer is not generated, make sure the build command is executed on Windows and that dependencies were installed. If a GPU remains in the locating stage, wait until the two-minute locator window finishes. If processing credits do not move, verify that at least 24 GPUs are Active and that the Start Processing button was pressed.

If the website does not open online, check that index.html is inside public_html. If navigation opens unexpected pages, confirm all HTML files were uploaded. If the portal account message does not appear, confirm site.js is uploaded and not blocked by cache.

19. Operational Checklist

1. Open Axzionn Cloud Desktop.
2. Create an account or login.
3. Open GPU Node Registry.
4. Click Register GPU1.
5. Wait for the two-minute locator stage.
6. Allow the GPU node to validate and configure.
7. Repeat the process for GPU2 through GPU24.
8. Confirm that 24 GPU nodes are Active.
9. Return to Dashboard.
10. Click Start Processing.
11. Monitor Current Balance, Locked Balance, Processing Credits and Days Remaining in real time.
12. Wait for 30 full days of active processing.
13. Open Withdraw / Redeem after the cycle is completed.
14. Select Wise, PayPal or Revolut.
15. Register the payout request.
16. Confirm that the cycle value resets to US$ 0.00 and the payout history remains saved.

20. FAQ

Can I register more than 24 GPUs?
Yes. The minimum is 24 Active GPU nodes, but there is no maximum limit.

Does processing start after registering all GPUs?
No. Processing starts only after at least 24 GPU nodes are Active and the Start Processing button is pressed.

What happens after I click Register GPU?
The node spends approximately two minutes in Locating GPU Node, then starts validation and configuration.

Does the balance exceed the configured monthly range?
No. Each 30-day cycle receives a maximum value between US$ 231.53 and US$ 269.48, and the balance remains capped by that value.

What happens after a withdrawal request?
The payout request is saved in history, technical logs are updated and the cycle balance resets to US$ 0.00.

Does the dashboard update automatically?
Yes. The desktop dashboard updates every second while the session is active.

21. Version History

Version 1.2.0 adds the two-minute GPU locator stage, manual Start Processing control, no maximum GPU limit, real-time one-second refresh, persistent log export, withdrawal balance reset and updated Hostinger publishing guidance.

Version 1.1.0 added fully linked website pages, individual GPU node registration, universal GPU acceptance language, no visible brand/model fields and expanded documentation.

Version 1.0.0 introduced the original website, desktop app, account flow, dashboard, GPU registry, logs, settings and 30-day redeem cycle.

22. Terms and Policies Overview

Terms, privacy, security, payment, withdrawal and data policies are available from the Policies page. These pages explain account usage, local data handling, payment method records, withdrawal cycle rules, data responsibility, security expectations and acceptable platform usage.