Metahive is the research, compute and Tier 1 line of Naevum Labs for organizations and hosts, so that a team’s folders become a working environment on infrastructure it can name.
Combine compute, power, cooling, network and operating responsibilities into a candidate envelope.
Physical and operator prerequisites.
Combine compute, power, cooling, network and operating responsibilities into a candidate envelope.
Location, tenancy and physical prerequisites.
Planned design remains distinct from commissioned capacity.
Planned design capacity remains separate from commissioned service capacity.
Compare required resources and sensitivity with an eligible service boundary.
Candidate service capacity and custody boundary.
Declared resource needs and sensitivity.
Compare required resources and sensitivity with an eligible service boundary.
Workload, custody, site and capacity requirements.
Eligible site or explicit mismatch.
Custody, resource and site requirements must all fit the proposed placement.
Bind maximum admitted cost before work under one identity.
Eligible identified placement.
Applicable tenant/site/period maximum and policy.
Same-identity settlement or retained uncertainty.
Bind maximum admitted cost before work under one identity.
Tenant/site/period and money/token maximum.
Policy identity and unresolved reservation state.
The reservation binds a maximum cost to the original tenant, site and period.
Compare scheduler/service evidence and settle the original reservation.
Original reservation for later settlement.
Independent identified work record.
Actual consumption/result or explicit unknown usage.
Compare scheduler/service evidence and settle the original reservation.
Tenant, product, unit, time and observed use.
Actual cost, justified unused balance or uncertainty.
Uncertain use does not automatically release the unused reservation.
Attribute site-hour metering using matching IT use without hiding idle energy.
Independent site/hour metered energy including overhead.
Observed tenant/site/hour IT use.
Attribute site-hour metering using matching IT use without hiding idle energy.
Meter and tenant IT-use records for the same site/hour.
Facility overhead, allocated energy and explicit unattributed remainder.
Attribution requires matching site and hour records; idle or unattributed energy stays visible.
Physical and operator prerequisites.
Combine compute, power, cooling, network and operating responsibilities into a candidate envelope.
Location, tenancy and physical prerequisites.
Planned design remains distinct from commissioned capacity.
Planned design capacity remains separate from commissioned service capacity.
Candidate service capacity and custody boundary.
Declared resource needs and sensitivity.
Compare required resources and sensitivity with an eligible service boundary.
Workload, custody, site and capacity requirements.
Eligible site or explicit mismatch.
Custody, resource and site requirements must all fit the proposed placement.
Eligible identified placement.
Applicable tenant/site/period maximum and policy.
Same-identity settlement or retained uncertainty.
Bind maximum admitted cost before work under one identity.
Tenant/site/period and money/token maximum.
Policy identity and unresolved reservation state.
The reservation binds a maximum cost to the original tenant, site and period.
Original reservation for later settlement.
Independent identified work record.
Actual consumption/result or explicit unknown usage.
Compare scheduler/service evidence and settle the original reservation.
Tenant, product, unit, time and observed use.
Actual cost, justified unused balance or uncertainty.
Uncertain use does not automatically release the unused reservation.
Independent site/hour metered energy including overhead.
Observed tenant/site/hour IT use.
Attribute site-hour metering using matching IT use without hiding idle energy.
Meter and tenant IT-use records for the same site/hour.
Facility overhead, allocated energy and explicit unattributed remainder.
Attribution requires matching site and hour records; idle or unattributed energy stays visible.
An illustrative process for comparing site constraints and reconciling identified resource use.
Additional mechanisms are described in the technical reference.
Site capacity and custody requirements guide workload placement. A reservation bounds the admitted cost; service records and site-hour metering account for use and idle energy.
Combine compute, power, cooling, network and operating responsibilities into a candidate service envelope.
Match workload and custody requirements to eligible capacity, then reserve a bounded cost under one operation identity.
Reconcile observed service use with the original reservation. Attribute site-hour energy using matching workload evidence and retain idle energy.
Useful compute. A clear place in the world.
Discuss compute or hostingWhat the research says
The IEA expects data-center electricity use to roughly double by 2030, with AI-focused sites growing fastest. Every new site will be asked what it draws and for whom. Metahive answers with an energy account that keeps the workload’s use, the site’s overhead and idle consumption apart.
Metahive has a research track prepared for European funding.
What survives testing goes into the Vault, Naevum’s method and component atlas, with what it assumes and what proved it, before it becomes an organ or a program.
Metahive designs container micro data centers, starts on rented EU servers, and operates sealed units that hosts own. A workload keeps one identity from reservation to energy account.
Idle consumption stays in the site’s energy account instead of disappearing from a workload-only total. Placement, custody and energy answer three different questions: where work runs, which boundary holds its data, and how measured site energy is assigned.
Micro data centers in standard containers, planned with Metahive Builder. The sites are in development.
Rented EU servers that Metahive operates carry the first workloads while the sites are built.
Standard sealed units that hosts own and Metahive operates. Idle capacity is sold as preemptible work.
Standard for ordinary data. Custody runs on confidential-computing hardware behind a private endpoint per customer, with open-weight models first.
Before a job starts, Metahive reserves the most it may cost against the customer’s and the site’s budgets.
When the job ends, its usage (customer, product, unit and time) is reconciled with the scheduler’s and the service’s own records.
Hourly site metering and each customer’s IT use support a stated allocation method. Allocated or estimated energy is labeled as such.
An infrastructure buyer chooses the trust tier; placement and the energy account follow from it. Illustrative.
Tier 1 is included with the stack. An organization shares its folders and gets a working environment; the full list of capabilities and their states is on the platform page.
Point Metahive at the folders you already have. It reads the text files and records the path and date of each one. PDF and Office files are in development.
A knowledge base and a memory are built from the index, and every answer leads back to its files.
Metahive proposes programs, skills and workflows. A person approves each one before it is installed.
Command-line coding agents connect through one governed gateway. Connectors for the Claude app, the ChatGPT app and VS Code are in development.
Every consequential action lands in a hash-chained, Merkle-anchored, timestamped record that you can verify.
Yes. Describe the workload or site and the location, custody and operating requirements. The discussion establishes what service or development scope is available.
Builder models proposed configurations and operating scenarios. It supports planning; a site’s construction, commissioning and service operation are separate stages.
The technical choices that give Metahive its particular behavior.
Metahive connects compute services to the sites and resources that support them. Workload admission, usage identity, energy attribution and operating responsibility give capacity a concrete setting.
Run a workload. Specify the workload, required capacity, location and service responsibilities. Agree the delivery scope around those requirements.
Develop a site. Examine equipment, power, cooling, network and host participation before treating a location as available capacity.
Design a dedicated environment. Connect deployment and custody requirements to the infrastructure and people who will operate it.
Admission, usage and settlement need to describe the same service.
Reserve before dispatch. Tenant and site budgets reserve the maximum admitted cost before work begins.
Settle against the result. Usage retains tenant, product, unit and time. Reconciliation compares records with scheduler and service evidence.
Explain the energy. Hourly site metering and tenant IT use can support an explicit allocation method. Allocated or estimated energy is labeled accordingly.
A proposed compute-site scenario showing the relationship between equipment, energy and inference.
Follow the storyWhere should your next workload run?
Discuss compute or hosting