Skip to content

boogiecompute

AI

Is this your project? Claim and verify →

Rent GPUs by the hour from Python. Pay from a wallet, get a machine.

What HEY knows

Building
Last shipped 44 days agoActive: 0 meaningful events in 30 days; latest ship 44 days ago. Evidence Source

Build Momentum 0How it is measured

Latest ship
v0.2.0 · · GitHub release

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

This change
Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “v0.2.0”.
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-09-08 00:57 UTC; HEY first knew on 2026-09-09. HEY indexed it later, as history.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

Follow puts boogiecompute on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me boogiecompute’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown5 gaps: Repositories (source unavailable), Releases (no source), Published packages (no source), API description (not enough yet), Official site changes (not enough yet). Every repository HEY holds has stopped answering.

HEY can answer 4 of the 9 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule's longer window: 4 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-08, is more than 30 days old.
SourceHEY holds no repository, changelog or feed it can read for this project; the status rests on building events it counted from the chain or from corroborated sources.ReadRecordsv0.2.0v0.2.0v1.0.0+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source7 registered sources, 0 of them context only.ReadRecordsv0.2.0v0.2.0v1.0.0+7 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology

Latest ship

v0.2.0boogiecompute/boogie-js

GitHub releaseSource verified

What shipped · One client over the built-in fetch, zero dependencies, same code in Node, Deno, Bun and the browser · rent() walks the whole path and hands back a machine you can use · wait() lets the service hold the connection instead of polling · template picks what the… Show all
  • What shipped
  • One client over the built-in fetch, zero dependencies, same code in Node, Deno, Bun and the browser
  • rent() walks the whole path and hands back a machine you can use
  • wait() lets the service hold the connection instead of polling
  • template picks what the machine boots as
  • stop() ends a rental early, unused hours come back
  • Type declarations included, no build step Numbers 11 tests against a fake network, checked against the live API. What is not here The client never signs a transaction. Settling the quote stays in your code, and examples/rent.js…

Record ship:1f0a33bd… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about boogiecompute — as of 2026-10-22

Is boogiecompute still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 44 days ago. Evidence
What did boogiecompute ship last?
Factv0.2.0 — GitHub release, 44 days ago. Evidence
What does HEY not know about boogiecompute?
Unknown5 gaps: Repositories (source unavailable), Releases (no source), Published packages (no source), +2 more. Every repository HEY holds has stopped answering. Details

Build timeline

  1. v0.2.0boogiecompute/boogie-py

    GitHub releaseSource verified

    What shipped · template= on quote() and rent(): a machine boots as a notebook, ComfyUI, a local model with a chat window, or an OpenAI-compatible endpoint · Order.workspace: the browser link once the tool inside answers · stop(): end a rental early, unused hours come back to the… Show all
    • What shipped
    • template= on quote() and rent(): a machine boots as a notebook, ComfyUI, a local model with a chat window, or an OpenAI-compatible endpoint
    • Order.workspace: the browser link once the tool inside answers
    • stop(): end a rental early, unused hours come back to the wallet
    • Machine.usd_per_gpu_hour, because the price per card is the one that compares
    • One error class per reason the service refuses, so code reacts to the reason Numbers 15 tests against a fake service, linter clean, checked against the live API. What is not here The package never signs a…
  2. v1.0.0boogiecompute/boogie-contracts

    GitHub releaseSource verified

    What this is The settlement contract as it runs on Robinhood Chain at 0x96Ce…F107. Source, tests, deploy script and a worked example of renting from code. What it does · Takes a price we signed, pulls your stock, sells exactly as much as the rental costs and returns the rest… Show all
    • What this is The settlement contract as it runs on Robinhood Chain at 0x96Ce…F107. Source, tests, deploy script and a worked example of renting from code. What it does
    • Takes a price we signed, pulls your stock, sells exactly as much as the rental costs and returns the rest inside the same transaction
    • Settles in USDG directly if that is what you hold
    • Never holds your equity between orders
    • Lets the owner sweep settled dollars but not money held against orders that are not provisioned yet. There is a test for that specifically. Numbers 18 tests…
  3. Code changes, week of 2026-09-07 – 2026-09-13boogiecompute/boogie-contracts

    Code activitySource linked

    4 active days in boogiecompute/boogie-contracts.

  4. Code changes, week of 2026-09-07 – 2026-09-13boogiecompute/boogie-py

    Code activitySource linked

    9 active days in boogiecompute/boogie-py.

  5. Code changes, week of 2026-08-31 – 2026-09-06boogiecompute/boogie-py

    Code activitySource linked

    8 active days in boogiecompute/boogie-py.

  6. Code changes, week of 2026-08-31 – 2026-09-06boogiecompute/boogie-contracts

    Code activitySource linked

    3 active days in boogiecompute/boogie-contracts.

  7. Code changes, week of 2026-08-31 – 2026-09-06boogiecompute/boogie-js

    Code activitySource linked

    6 active days in boogiecompute/boogie-js.

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about boogiecompute? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

8 changes on HEY’s record for boogiecompute: 3 releases · 5 weeks of code pushed.

All 8 changes for boogiecompute →

The full change record holds 10 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 4 of the 9 research questions that apply.

4 of 9 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasured
  • RepositoriesSource unavailableEvery repository HEY holds has stopped answering.
  • ReleasesNo sourceNo source HEY reads releases from.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 1h ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Published packagesNo sourceNo repository the project claims as its own.

Not applicable here: Repository details, Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources