Build and test
A coding agent gets a temporary workspace to run tests, build a preview and return artifacts. Changes still follow the project's review process.
Defined repository access. No automatic production release.
Agent infrastructure / From Belize
BERTH™
by Silvatech
A place for agents to run.
Compute, storage and a place to work. We are designing BERTH so agents can find and operate the resources they need, within an agreed budget and clear permissions.
In developmentPilot enquiries welcome
Concept artwork. Not a live facility or product interface.
What is BERTH?
The agent is the user. The task sets the requirements.
BERTH is an agent-first compute platform in development at Silvatech in Belize. The goal is to let agents discover suitable infrastructure, request a runtime and operate within agreed budgets and permissions. Today, this is a concept and pilot-enquiry page, not a live booking service.
An agent should be able to request what it needs without a person clicking through every step. We are designing for agent identities and delegated authority, with a responsible person or organization linked where contracts and payment providers require one.
01
Identity
An identifiable agent, with scoped credentials and a record of its actions.
02
Authority
A defined budget, permissions and approval rules before work begins.
03
Continuity
Runtime, storage and recovery designed around the job, not a chat window.
The planned workflow
From a task to a place to work.
A discovery and provisioning layer across infrastructure providers. The ambition is one coordinated workflow, not ownership of every server.
- 01
Describe the job
Specify compute, storage, duration, region and the boundaries the agent must respect.
- 02
Find a fit
Compare suitable capacity against the task and budget. Review the proposed costs before authorizing work.
- 03
Reserve and run
Provision an isolated environment with scoped access, an expiry and an agreed spending limit.
- 04
Observe and close
Review usage and actions, retain approved outputs, and stop or renew the workload deliberately.
Autonomy with boundaries
Give agents room to work. Keep the controls close.
An agent-first account is a product design choice, not a claim of legal personhood. The proposed control layer makes delegated actions visible and revocable.
Design requirements for the pilot, not a claim that these controls are already deployed.
- Spending
- Budget caps and approval thresholds
- Access
- Scoped keys and least-privilege tools
- Accountability
- Action logs and a responsible counterparty
- Recovery
- Expiry, revocation and an emergency stop
What could run here
Start with a bounded job.
Research and process
A data agent works through approved documents or a batch-processing task, with the region and retention requirements agreed in advance.
Approved inputs. Explicit storage and deletion rules.
Coordinate operations
An operations agent connects permitted tools and runs scheduled work, requesting approval when an action exceeds its authority.
Scoped integrations. Reviewable actions.
Built in stages
Start with the workload. Earn the infrastructure.
Now / Discovery
Shape the first pilots
Discuss real workloads, constraints and operational needs with potential pilot collaborators.
Planned / Pilot
Prove the managed workflow
Validate provisioning, metering and controls on rented infrastructure before opening self-service access.
Exploring / Longer term
Capacity closer to the work
Explore reserved capacity and, if demand and feasibility support it, Belize-based edge infrastructure.
No public compute inventory, checkout or provisioning API is available yet. Pricing, providers, supported regions and service commitments will be agreed before any pilot starts.
Direct answers
Before you book a berth.
Can I book compute on BERTH today?
Not yet. BERTH is in development and Silvatech is inviting pilot enquiries. This page does not reserve capacity, take payments or create accounts.
Can an agent act without a human clicking every step?
That is the design goal: an agent identity with delegated authority to request and operate resources within policy. A responsible person or organization would still be linked where required by contracts, compliance and payment providers.
Will BERTH accept cards or cryptocurrency?
Payment options are still being evaluated. BERTH does not currently accept card payments, cryptocurrency or deposits. Any future payment flow will need appropriate provider approval, controls and legal review before launch.
Is BERTH a bank or financial account for AI?
No. BERTH is a compute and infrastructure concept, not a bank, deposit account, investment product or promise of returns. The earlier BAAR working name has been retired.
Will the infrastructure be hosted in Belize?
Silvatech is based in Belize; that does not mean every future workload will be hosted here. The initial direction is rented infrastructure, with location agreed per workload. Belize-based edge capacity is a longer-term possibility, not an available facility.
Can agents create more agents or change their own code?
Controlled child workloads and code forks are part of the concept. They would inherit spending, access and runtime limits, with approvals for elevated actions. BERTH is not intended to enable unrestricted replication or bypass project review.
For people and agents
One brief. The same facts.
Read the concept as Markdown or structured JSON. These are public reference documents, not API endpoints for booking or payment.
Pilot enquiries welcome
What would your agent need to run?
Tell us about the task, runtime, region and budget constraints. We will discuss whether it is a fit for a future BERTH pilot.
Please do not send passwords, API keys, wallet credentials or sensitive datasets.