What to use instead of Shrimpy

The product

Shrimpy was a hosted portfolio rebalancer for crypto. You connected exchange accounts with API keys, set a target allocation, and Shrimpy traded the account back to those weights — on a schedule or when a coin drifted too far. The home page as the Internet Archive captured it on 15 June 2023 lists the rest of the job: custom allocations "with unique weighting methods", minimum and maximum allocation amounts, periodic or threshold rebalancing, a portfolio stop-loss, a "Rewind" view of the portfolio at any point since sign-up, and a simulator for testing allocations against history. It claimed $13B+ traded through it. The company behind it was Benthos Labs Inc., per the footer of its own help centre.

It ended in July 2023, and the date comes from a secondary source. Brave New Coin reported on 1 July 2023 that Shrimpy had emailed users to say it was terminating the business, with 7 July as the last day of operations, that the website would come down after that, and that customers should finish their trades and download their data first. The report quotes the letter blaming falling retail demand. We could not find the email or a Shrimpy-hosted notice — the home page never carried one — so treat the day as the reported one.

The code went to a retirement-account company. On 15 November 2023 BitcoinIRA announced it had acquired Shrimpy.io, that the founders were joining its executive team, and that eligible Shrimpy customers would be "transitioned into the broader offerings of BitcoinIRA". The same release promised portfolio rebalancing, dollar-cost averaging, stop-losses and trade-history downloads to BitcoinIRA users in early 2024. That is rebalancing inside a self-directed IRA, which is custody — not what you were using Shrimpy for, and outside what this catalogue covers.

The marketing page outlived the product by two years, which is why people still arrive. The Internet Archive kept capturing the same home page from June 2023 into 2025, sign-up buttons and a banner for Shrimpy Advisory included; the last one that answered was 30 August 2025, and by 15 November 2025 the page returned a 404. On 4 October 2026 the home page is a hosting provider's 404, the blog is an expired-website placeholder, the help centre returns a Cloudflare error and the app's hostname no longer resolves.

What to use instead

Expect to rebuild your allocation by hand. Nothing here imports a Shrimpy portfolio, and the history you kept there went down with the site.

If what you need is someone else running the rebalancer, OctoBot Cloud is the closest thing in this catalogue: a crypto-basket bot on the paid plans and portfolio rebalancing on Pro, at $29.99 a month, hosted on the vendor's servers across eight spot venues. It has no backtester at all, so the "test it on history first" step Shrimpy offered is gone here.

If you would rather run it yourself and pay nothing, OctoBot is the same engine under GPL-3.0, and its Index trading mode is a rebalancer in plain terms. The mode's own documentation says it holds an equal-weight index of the coins you trade against a reference currency, checks the portfolio every trigger period days (decimals allowed, zero meaning every price update), and rebalances when any coin leaves its target by more than a rebalance cap you set. Custom weights per coin need a paid Premium extension. Unlike the hosted plan, it backtests.

If you want the weighting rules Shrimpy had and OctoBot does not, write the loop. CCXT gives you fetchBalance and createOrder with the same names on 104 exchanges under an MIT licence. Reading balances, pricing them, computing drift and sending the orders is yours to write, and so is every rule — bands, minimums, which coin funds which — which is the point: nobody can leave one out.

If all you used was the dashboard, Cryptohopper has a free plan, Pioneer, with manual trading and portfolio management on every connected exchange and no automation of any kind. It shows you where the allocation stands; it will not put it back.

What you give up

One portfolio across several exchanges. Shrimpy's pitch was the whole portfolio in one place. OctoBot's Index mode computes holdings against a reference currency on the exchange it trades, and its code runs each rebalance against one exchange. If your allocation was meant to hold across Binance and Kraken together, nothing here does that for you — that is the CCXT route, and the cross-venue transfers stay manual.

The weighting menu and the backtest of it. Shrimpy advertised weighting methods and min/max bounds per asset, and a simulator to try them. OctoBot gives you equal weights, or custom percentages behind a paid extension, and the hosted plan has no backtester at all. Weighting by market cap, if that is what you ran, is code you write.

Your history. Rewind showed the portfolio at any point since sign-up, from data Shrimpy held. The letter told users to download their data before 7 July 2023; if you did not, it is gone, and the exchanges' own trade histories are the only record left to rebuild from.

Migration notes

Revoke the keys you gave Shrimpy. An exchange API key outlives the service it was issued to, and the company that held yours has been sold. Delete them at each exchange before you issue new ones to anything on this page.

A threshold rebalancer can be configured never to buy. OctoBot's documentation warns that if the rebalance cap is equal to or larger than a coin's target weight, a falling coin never triggers a rebalance — only a rising one does. With five coins at 20% each, a 20% cap means a coin can go to zero without the bot topping it up. Keep the cap well below the smallest weight.

Small drifts produce trades the exchange refuses. OctoBot's index code aborts a rebalance when an order would fall below the exchange's minimum trade volume, the same thing Shrimpy's help centre had an article explaining. A small portfolio spread over many coins hits this constantly; fewer coins or a wider cap is the fix, not a more frequent trigger.

The reference currency is part of the index. OctoBot measures every weight against the reference market in its profile — USDT in its own example — so the stablecoin balance is the funding leg, not a holding. If your Shrimpy allocation held a stablecoin as a deliberate slice, model it explicitly rather than assuming it carries over.