Choose your workload
Explore inference, fine-tuning and agent workloads. CORELOT aims to connect GPU capacity with Solana-native access and clear usage costs. This page is a product concept, not a live private-compute service.
ExploreAI compute onSolana. A privacy-first direction forevery AI workload, with clear costs and user-controlled access.
view the compute activityYou choose the workload. CORELOT is exploring privacy-first GPU infrastructure with Solana-native coordination, so you stay in control of how your applications use compute.
Explore inference, fine-tuning and agent workloads. CORELOT aims to connect GPU capacity with Solana-native access and clear usage costs. This page is a product concept, not a live private-compute service.
Choose what should stay private: prompts, files and model outputs. Encryption, execution isolation and data-retention controls are design goals that require implementation and verification.
The planned payment layer uses Solana and USDC for compute access. Published costs should describe resource usage without exposing workload content. Payments are not live yet.
Every workload needs a clear boundary. Inspect the hardware concept while privacy protections are being designed.
A private workload should not mean opaque infrastructure. Public resource metrics, private application data, with Solana as the planned coordination layer, so visibility does not require revealing your inputs.
The map illustrates a distributed GPU topology. Locations, operators and utilisation are illustrative data, not a live CORELOT network.
Choose a single GPU sled or explore pooled capacity. Different workloads need different resources, without changing the privacy-first direction.
A distributed capacity profile for scaling AI applications. This interface does not route or execute real workloads.
8 Sleds, 64 GPUs, 2 Data centers
Solana-native resource coordination is planned. No live compute registry or settlement is provided by the current interface.
The architecture aims to separate resource accounting from workload content, so compute usage can be visible without publishing your inputs. Solana is the planned settlement layer. The activity below is illustrative.
Illustrative · Solana Base58 signature format. Illustrative records, not on-chain transactions.
The design prioritises user-controlled access to prompts, files and outputs. Access controls are not implemented by this current interface.
The goal is to disclose resource usage, not workload content. No claim of zero logging or encrypted execution is made.
Solana is the intended network for compute payments and coordination. The signatures shown are examples, not on-chain transactions.
Review the cost model before launching a workload, with every component visible in this illustrative breakdown.
Illustrative $40 compute budget: power $5.60, space $3.60, maintenance $2.40, hardware cover $1.20, coordination $3.20 and execution $24.00.
Illustrative $40 compute budget. These figures are not a price quote, an earnings forecast or a live billing schedule.
The questions people ask first. The docs go deeper on privacy goals, compute and Solana.
read the docsCORELOT is a privacy-first AI compute concept with a Solana-native direction. It explores how GPU access, workload boundaries and transparent resource accounting can work together. This website is a interactive interface, not an operating compute network.
No. This is a concept preview. Private execution, workload routing and payment integration require implementation, security review and a documented launch.
Solana is the planned network for wallet-based compute access, USDC payments and resource coordination. Ordinary Solana transactions are public; using Solana alone does not make payments or workloads private.
Prompts, uploaded files, model outputs and application secrets are the intended privacy boundary. Exact protections and retention policies must be defined before a production launch.
Not currently. Confidential execution requires a verified technical implementation. CORELOT does not currently claim MPC, FHE, TEE integration, end-to-end encryption or zero logging.
No. GPU counts, utilisation, activity signatures and dollar values illustrate the product interface. They do not prove deployed hardware, customer usage or on-chain settlement.
No. This concept preview does not accept compute orders or deposits. Solana and USDC payment integration is planned, not live. Never send funds based on this interface.
Explore one sled or scale across a pool. Review the concept before any production integration.
Controlled accessPrivacy-first designSolana-native direction