Pictor Documentation
pictor.networkXTelegramDiscord
  • Welcome to Pictor Docs
  • Company
    • Executive Summary
    • About Pictor
    • How Pictor Works
      • Pictor’s Decentralized GPU Render Farm Model
      • Pictor's GPU Aggregator Model
    • Pictor Features
      • Key Features
      • Unique Features
  • Products
    • Pictor Cloud
    • Pictor Explorer
    • Pictor Render
    • Pictor Ultra Render AI
    • Pictor AI Training
    • Pictor Remote Workstation
    • Pictor Worker
    • Pictor Checker Node
    • Pictor ID
  • Participants
    • Where Do You Fit?
    • Creators
      • Creator Overview
      • Supported Software
      • Use Cases and Applications
      • Get Started
        • Get Started with 3D Rendering
        • Get Started with AI Upscaling
    • Workers
      • Worker Overview
      • Worker Reward
      • Proof of Work
      • Worker Determined Pricing
      • Worker Requirement
      • Get Started
    • Checkers
      • Checker Overview
      • Checker Rewards
      • Checker Requirements
      • Get Started
    • Render Farms
      • Overview
      • Get Started
  • Architecture
    • Architectural Layers
  • Reference
    • SDK
    • Glossary
  • Official Links
    • Website
    • X
    • Telegram Channel
    • Telegram Community
    • Discord
    • LinkedIn
    • YouTube
Powered by GitBook
On this page
  • Pictor Cloud Architecture
  • Pictor Worker Architecture
  • Worker Mining Controller
  • Pictor Checker Architecture
  • AI Core
  • Job Manager
  • Metadata Manager
  • Worker Manager
  • Reward Manager
  • Transaction Manager
  • Proof Manager
  • Pictor Network Architecture Phases
  1. Architecture

Architectural Layers

The underlying framework and structural design that powers the Pictor network

PreviousGet StartedNextSDK

Last updated 3 months ago

The Architecture of Pictor is a multi-layered, cohesive design that delivers a seamless, secure, and efficient user experience. Each layer within the architecture serves a specific purpose, collaborating to maintain optimal system performance.

User Interface

The User Interface layer is the visual gateway through which users interact with Pictor. It includes the Pictor Cloud, Pictor Render, Pictor Worker, and Pictor Checker applications, all designed to be intuitive and user-friendly. This layer ensures that users can easily navigate and interact with the system, making it accessible for both technical and non-technical users.

Tech Stack: ReactJS, Tailwind, web3.js, WPF C#.

Security Layer

The Security Layer is crucial for maintaining the integrity and safety of Pictor. It incorporates a Firewall to protect the network, an Authentication Service to validate users, and a Logging & Event Service to track and record activities. This multi-faceted approach ensures that all operations are secure and monitored, safeguarding the network from potential threats.

Tech Stack: Firewall (pfSense, iptables), Authentication (OAuth, JWT), Logging Service (ELK Stack, Graylog).

API Layer

The API Layer serves as the communication bridge between various components of the Pictor Network. It includes Public APIs for Pictor Cloud and Pictor Explorer, Private APIs for Pictor Render, Pictor Worker, and Pictor Checker, as well as Internal APIs for Management, Analytics, and Monitoring/Reporting. This layer facilitates smooth communication and data exchange across the network.

Tech Stack: RESTful API, FastAPI, GraphQL, Socket IO.

Backend Layer

The Backend Layer is the powerhouse of the Pictor. It manages critical operations such as Worker management, Job management, User management, Transaction management, Resource Monitoring, Analytics, On-chain Monitoring, and Fault Monitoring. This layer ensures that all backend processes are handled efficiently and reliably.

Tech Stack: FastAPI, Python, Node.js, Flask, Pandas.

Database Layer

The Database Layer acts as the data repository for Pictor. It is divided into Main Storage for structured data and Caching for temporary, frequently accessed data. This dual approach allows for quick access to essential data while maintaining the integrity of stored information.

Tech Stack: Main storage (Microsoft SQL Server, PostgreSQL), Caching (Redis).

Message Queue

The Message Queue Layer orchestrates asynchronous communication within the network. It ensures that data flows smoothly, preventing bottlenecks.

Tech Stack: Kafka, RabbitMQ.

Infrastructure Layer

The Infrastructure Layer is the foundation of Pictor. It includes the Worker Pool, Orchestration, and Render Task. Worker Pool consists of GPUs from Global Workers and our Trusted Partners, Orchestration tools manage deployments, whereas Render Task handles rendering and computing operations.

Also, Infrastructure Layer provides Data Storage solutions with Walrus support and monitors GPU performance using Nvidia-smi or NVIDIA DCGM. The Infrastructure Layer ensures that the Pictor remains robust, scalable, and capable of handling complex rendering tasks.

Tech Stack:

  • GPU/CPU Pool.

  • Orchestration: Kubernetes, Prefect, Apache Airflow.

  • Render Tasks: Blender, Cinema 4D, Redshift, OctaneRender, etc.

  • Data Storage: Walrus, Pictor cloud storage.

  • Containerization: Docker.

  • Monitoring: Grafana, Datadog, Prometheus, NVIDIA DCGM.

Pictor Cloud Architecture

Tech Stack: Vue.js, Tailwind, web3.js.

Pictor Worker Architecture

Tech Stack: WPF, C#, SocketIO, Kafka, SFTP, IPFS, REST API.

Worker Mining Controller

Pictor Checker Architecture

Tech Stack: WPF, C#, SocketIO, Kafka, SFTP, IPFS, REST API.

AI Core

Job Manager

Metadata Manager

Worker Manager

Reward Manager

Transaction Manager

Proof Manager

Pictor Network Architecture Phases

Pictor_Architectural Layers