HAL SUPREME
Menu
Product foundation in active development Google identity Preview is verified. HAL Link is a tested local developer preview. Billing and cloud sandboxes are not enabled yet.
Build with HAL

One workspace for your ideas, tools, models, and machines.

Create projects, keep artifacts and memory together, connect the systems you choose, and let HAL help build—without turning your computer into an unrestricted remote shell.

Verified Google identity Preview 8/8 HAL Link security tests $0 charged by this page
HAL · Project Atlas
PROJECTAtlas launch system
Private
NEXT VERIFIED OUTCOMEConnect one local project with bounded read and proposal access.
MEMORY12User-controlled notes
ARTIFACTS24Files with lineage
CONNECTION Google identityVerified Preview
LOCAL LINK Approval requiredDeveloper preview
01 / WORKSPACE

Projects, artifacts, memory, and reflections

The personal workspace is the durable center. Chats become useful when decisions, files, receipts, preferences, and lessons can stay attached to the project that produced them.

P

Projects

Separate goals, people, connections, permissions, budgets, and work history. A project is context—not a second scheduler.

Planned after identity
A

Artifacts

Files, code, media, receipts, and releases with source lineage, review state, and clear private/public boundaries.

Existing HAL foundation
M

Memory

User-controlled facts and preferences with edit, export, expiration, and delete controls. No invisible permanent profile.

Planned user surface
R

Reflections

Lessons, decisions, contradictions, and next actions that improve future work without rewriting canonical history.

Existing HAL pattern
02 / EXTEND

Connections and plugins

Connections bring data or capability. Plugins package a bounded workflow. Skills teach HAL how to use them. Every item shows what is live, what is a developer preview, and what is only planned.

G

Google identity

Sign in and establish an opaque HAL user and private workspace identity.

Verified Preview
H

HAL Link

Grant specific local project folders, propose file changes, and run named checks.

Developer preview
</>

Git providers

Projects, issues, commits, reviews, and release evidence through user-authorized access.

Planned
D

Drive and documents

Bring selected documents and media into a project without giving blanket account access.

Planned
T

Team systems

Slack, Teams, email, calendars, and project tools with per-action approval controls.

Planned
M

MCP catalog

Connect compatible tools locally now; authenticated remote MCP remains a separate gated release.

Local stdio today
03 / ROUTE

Bring your own models and compute

HAL should choose from resources the user has authorized—not trap users inside one model company. Provider health, privacy, latency, quality, and estimated cost remain visible.

01

Hosted LLMs

Connect OpenAI, Anthropic, Google, xAI, or other compatible providers through account-bound credentials that never enter prompts or public projections.

Connection UI planned
02

Local models

Connect OpenAI-compatible local endpoints for private or low-cost work. Discovered does not mean healthy; each route needs a live canary.

HAL routing foundation
03

Your GPU

Offer selected local compute to your own HAL workspace with thermal, memory, time, privacy, and job-type limits. No public GPU marketplace or payouts in V1.

Planned connector
04

Cloud sandbox

Isolated, disposable build environments for paid users. Cloudflare Sandbox/Containers is the intended lane; usage has real compute cost and must be quota-bound.

04 / CONNECT

The current prototype is local stdio MCP. A future cloud connection must be outbound-only, authenticated, revocable, and unable to approve its own mutations.

Allowed by a workspace grant

  • Read selected text files within byte limits
  • Propose an exact file replacement
  • Apply only after separate local approval
  • Run named, preconfigured argv checks
  • Record metadata-only receipts

Not granted

  • Arbitrary shell or command strings
  • Credential, browser-profile, or secret access
  • Hidden installation or persistence
  • Unbounded filesystem or desktop control
  • Purchases, publishing, or public messages

Local approval stays local. A proposal becomes invalid if the file changes, and every approval is single-use. The current process boundary is not represented as an OS-enforced sandbox.

05 / CONTROL

Developer settings people can understand

Each project will expose the same permission model in plain language: what can be read, what can change, which providers can run, what may cost money, and what needs a person.

Workspace accessOne selected folder
Write proposalsLocal approval required
Arbitrary shellBlocked
Paid provider callsAsk every time
Memory retentionUser controlled
06 / BUSINESS MODEL

Monthly software + metered compute

A subscription funds the workspace, orchestration, memory controls, integrations, and support. Expensive model, music, video, GPU, and sandbox usage stays separately capped so one heavy job cannot consume everyone’s service.

PayPal billing is not enabled yet.These are proposed founding-alpha prices for customer interviews. No checkout or charge occurs on this website today.
Preview
$0/ month

Try the signed-in identity workspace and follow verified product progress.

  • Google identity Preview
  • Public HAL and proof pages
  • Private-alpha application
  • No included paid compute
Open Preview
Creator Alpha
$49/ month

For creators using voice, music, image, and video workflows with explicit limits.

  • 10 private projects
  • Creator Studio workflow access
  • Media lineage and quality receipts
  • Priority job admission
  • Media generation purchased separately
Request access
Team Pilot
$199/ month

For a small design partner that needs shared projects and a guided integration.

  • Up to 5 members
  • Shared projects and permissions
  • Private integration onboarding
  • Monthly evidence review
  • Compute and custom work separate
Discuss a pilot
Proposed usage rule

Transparent cost protection

Customer usage price = Provider cost ÷ 0.70. That targets a 30% gross margin before payment processing, billing, storage, support, refunds, and taxes. Every job still shows a maximum price before admission.

Example—not a quote

What a $10 provider job means

A $10 estimated provider cost becomes $14.29. At PayPal's currently published US domestic Checkout rate of 3.49% + $0.49, about $3.30 remains before storage, support, refunds, taxes, and other costs. It is not net profit.

Small jobs

Bundle usage instead of tiny charges

PayPal's fixed transaction fee makes per-job micropayments inefficient. Launch with prepaid, non-transferable platform usage or a capped monthly balance, then reconcile every provider receipt. Current PayPal fees.

07 / NEXT

The intelligent path from here

Turn the current working system into evidence investors and partners can evaluate: a small paid pilot, one connected project, one trustworthy local build flow, clear unit economics, and repeatable proof.

  1. NowRecruit 5–10 design partnersInterview them against the pricing and connector priorities above.
  2. ThenActivate merchant + entitlementsCheckout, signed webhooks, customer portal, refund terms, and spend caps.
  3. NextShip one local connection end to endInstall, grant, propose, approve, test, revoke, and verify receipts.
  4. ProveConvert one pilot into revenueMeasure activation, retained use, provider cost, support time, and gross contribution.
  5. ScaleApply for credits and investmentUse real usage and customer evidence rather than unsupported capability claims.