With KryllOS, you've never needed a command line. You build your strategies, you backtest them, you run them, all from the interface, and that's exactly how it should be. Most people will never go any further, and they're right not to.

But there's the other crowd. The folks who like being hands-on with their machine, peeking under the hood, running their own stuff, basically tinkering. For them, there was a wall: their KryllOS runs on a VPS, and getting to that VPS meant leaving the app and wrestling with an SSH client, a key, an address, a port.

0.5.41 cuts straight to the prompt. KryllOS ships a real terminal, and it opens your VPS's shell right inside the app. If you're the type who's been itching for this, the rest is for you.

A real terminal, your VPS's shell

Let's be clear about what this is, because that's the whole point. What you type in this terminal runs on your VPS, in a real shell, opened as your user, right in your KryllOS working folder.

The difference is that there's nothing for you to connect. Normally, opening a command line on your VPS calls for an SSH client, a key you have to keep safe, an address and a port to remember. KryllOS already holds that secure connection to your server, and the terminal rides on it. You open the Terminal app, and you're in. Nothing to install, nothing to dig up, nothing to mistype.

Where to find it

• Open the Terminal app, alongside your other KryllOS apps
• It opens on your VPS's shell, in your working folder: type ls to see your strategies

It behaves like your real terminal

The fastest way to convince yourself is to type a command. pm2 list, and your KryllOS engine's status shows up in a color-coded table. top, and you get the full-screen system monitor refreshing on its own. nano, and a real text editor opens right in the window.

And it has all the muscle memory you know: Tab completes your paths, the up arrow brings back your last command, Ctrl+R digs through your history, and that history remembers you from one session to the next. If you already live in a terminal, you'll feel right at home.

Watch your engine, live

Your bot runs on its own, and most of the time you don't need to watch it. But the day you want to understand what it's up to, out of curiosity or because something looks off, the terminal shows you live. Type pm2 logs kryllos, and your engine's activity starts scrolling by: the strategies running, the events, any errors, the moment they happen. Do something in the app, and you watch the lines write themselves right in front of you. Ctrl+C once you've seen what you came for.

Make it your playground

It's a real shell, so you do whatever you want with it. You set up aliases to park your go-to commands behind a short name. You write your own little script, drop it into your KryllOS space, run it, and it shows up in your file manager like everything else. Anything you'd do on any Linux server, you can do right here, without leaving the app. Maybe that's the real luxury: your server becomes a place you get your hands into again, not a sealed box.

Good to know

A couple of things before you dive in. The terminal opens one window at a time, no tabs. If you close it, whatever was running inside stops with it: to launch something that should keep going without you, put nohup in front of your command and an & at the end. It's a normal shell, not an admin account: commands that touch the system will ask you for a password. And keep your SSH access on hand: this terminal is served by KryllOS itself, so the day the app stops responding, SSH is how you'll go restart it. A fantastic shortcut for day-to-day use, not your only way in.

You could go your whole life without ever opening this terminal, and your KryllOS would run just the same. The interface is enough to keep your strategies going, and it will. But if the urge takes you to poke around, your VPS is no longer a distant machine behind a wall of SSH: it's a server you open with one click, where you can step in, look around, tinker, like it's home.

Join the Waitlist

Everyone trades their own way, and above all, everyone trades on their own hardware. A laptop off in the corner of a table, one ultra-wide screen, or two or three monitors lined up on a desk. Your workspace is yours, and you like to set it up however feels right.

Until now, the KryllOS editor kept to a single window. One solid block, with its tabs, its chart folded up at the top, and its backtest results boxed into the same frame. Whether you were on a 13-inch screen or had three monitors to work with, all that room around it went to waste.

KryllOS 0.5.38 opens things up. Your chart and your backtest results can now leave the editor as companion apps: real standalone windows you arrange however you want. You're no longer stuck with one fixed layout, you build your own. And the more screen space you have, the more you'll get out of it ;)

Detach your chart and results

It all starts with one icon. A single click, and both windows detach at once: the editor closes its inner panels and goes full screen, your chart shoots out to one side, your backtest results to the other. Two windows in their own right, all yours.

From there, you're in charge. You move them, resize them, drop them wherever works for you: side by side on a big screen, or straight onto a second monitor if you have one. Editor on one side, your chart and results on the other, everything in view at once.

Switch strategies, your windows follow

Your detached windows stay wired to the editor: change something on one side and it updates on the other. But the real convenience kicks in when you switch strategies.

Your editor doesn't hold just one strategy: each tab is one. When you move from one tab to another, your whole setup follows all at once. The results window shows the backtest for the new strategy, the chart switches to the right curve with its indicators and positions, the editor shows the right blocks. You switch strategies, and your entire workstation reconfigures itself.

The lock: freeze a window in place

Your windows follow your editor, but sometimes you want one of them to stop moving: to hold it on a specific result while you go back to tweaking your strategy on the side. That's what the lock is for.

Each companion app carries a small icon that shows its state: a chain link when it's tied to the editor, a padlock when it's frozen. You click, the link turns into a padlock, and the window stays on its version no matter what you do next.

That's what makes comparing versions possible. You freeze one strategy's backtest, go back and change an indicator or a level, and run it again. On one side your new result, on the other the old one, still frozen, right there to compare. You unlock when you're done, and the window resyncs.

At its core, 0.5.38 tears down the walls of the editor. Your chart, your results, and your strategy no longer fight over a single window: each gets its own, you organize them however makes sense to you, and everything stays connected to what you're building. Your second screen finally has a reason to exist, and running two ideas in parallel is no longer a window-juggling headache. Update to 0.5.38, pop your chart and results out, and give them some room at last ;)

Join the Waitlist

Version 0.5.32 unlocked parallelism: multiple engines, each on its own core, plus slots to advance several backtests per engine. The idea was to launch a whole batch of backtests at once, without waiting for each one to finish before starting the next. What was missing was the tool to build that batch. You were still launching your backtests one at a time: open a tab, configure it, run it, then start over for every pair, every timeframe, every variant.

That's what 0.5.35 brings: the Multi-Backtest app. You build your list of backtests once, launch the whole thing, and it clears itself across the available engines while you work on something else.

The Multi-Backtest app

Multi-Backtest is a list of runs. Each row is a backtest ready to go, with its strategy, platform, pair, and timeframe. Nothing forces you to stick to a single strategy: you can stack the same one across ten pairs, ten different strategies, or any mix of the two. You build the list, you launch it, that's it.

Adding a strategy to the list

Two paths, depending on where you are :

From the editor, the Add to multi-backtest button sends the open strategy to the list along with its current configuration platform, pair, and timeframe already set. Switch pairs, click again, and the row gets added to the list.

From the file manager, right-clicking a strategy offers the same Add to multi-backtest option. The difference: it arrives unconfigured, since you haven't opened it. You'll need to set it up before running it.

How to add a backtest to the list

• From the editor, set your platform, pair, and timeframe, then click Add to multi-backtest
• Or right-click a strategy in the file manager, then Add to multi-backtest
• Repeat as many times as needed, each addition stacks onto the list

Configuring and duplicating your backtests

A row can be edited at any time. Double-clicking it, or right-clicking and selecting Edit, opens its run settings: platform, pair, timeframe. Adjust, hit Save, and the row is ready.

Duplicate is the move that saves the most time. Configure one row correctly, duplicate it, and on the copy only change what varies, the pair or the timeframe. One on ETH, one on Solana, one on last year. In a few clicks, you've built a full series without ever re-entering the same settings twice.

How to set up a series

• Double-click a row (or right-click then Edit) to open its run settings
• Set the platform, pair, and timeframe, then Save
• Right-click then Duplicate to copy the row
• On the copy, only change what varies, the pair or the timeframe

Run your whole list in one click

List ready? The Run All button launches everything. One click, and you no longer have to come back and trigger each backtest yourself: whatever can start right away does, and the rest waits its turn, kicking in automatically as engines free up. Your list clears itself.

In practice: testing ten pairs one at a time means ten round trips configure, launch, wait, repeat. With Multi-Backtest, it's one list built once and a single Run All. The time you used to spend clicking, you now spend analyzing.

How many backtests can run at the same time on KryllOS?

That depends on what you've set in Settings > Performance, under "Parallel backtests," with the two sliders introduced in 0.5.32:

• Backtest engines: the number of engines running in parallel, each on its own core. This is the real speed lever, the more you have, the sooner your batch finishes. KryllOS detects your available cores and recommends a value suited to your machine.
• Multiplexed slots: several backtests sharing the same engine, each advancing in turn. None of them run faster, but they all progress together.

The total follows the formula shown at the top of the panel: moteurs × slots. Two engines and two slots means four backtests running at once, with the rest of your list following behind. That's exactly what multiplexed slots were built for: launching a whole batch without waiting for each one to finish. Multi-Backtest is the tool that feeds those engines.

Cleaning up the Multi-Backtest list

Each row shows its own progress bar, handy for longer strategies where a run takes a while. You can see at a glance what's running, what's waiting, and what's done.

Two buttons for wrapping up a series. Clear removes finished runs from the list and keeps the view tidy. Cancel all stops everything, including runs still in progress, and cleans up after itself.

.backtest files

Every backtest produces a .backtest. Until now, it was on you to save it, using the floppy disk icon. Multi-Backtest does it automatically for every run in your list, under a default name that includes the strategy, the pair, and the timestamp. Your results are kept without you having to think about it, and you know which is which without opening them.

A .backtest file is self-contained: it holds the strategy, the run, and the logs, all in a single file.

Finding your backtests in the file manager

In the file manager, the backtests section groups together all your saved backtests, both from Multi-Backtest and the ones you save manually. The file manager now refreshes every time it's displayed, so whatever you just launched is already there, and its side navigation is freer to use.

Opening your backtests and their linked strategy

A backtest can be reopened in the editor with its full results, exactly as they were at the end of the run. Since your strategy may have changed in the meantime, KryllOS handles the different cases:

• The tab is already open elsewhere: it takes you back to it instead of creating a duplicate.
• You've moved a block since then: it still finds the right strategy.
• You've edited the strategy: it opens a new tab with the version that was actually backtested, since it's no longer the same one.
• The strategy is no longer on your drive: it asks whether you want to cancel, or open the version that was backtested.

Sharing a backtest

Since the file contains everything, you can hand it over. Export to zip packages the whole thing. On the other end, the person opens your strategy, reviews the backtest and its source code, and can rerun it themselves to verify. A result you're presenting is no longer a screenshot, it's a full test the other person can replay.

0.5.35 brings two things: the Multi-Backtest app, which builds and runs your backtests in batches while you work on something else, and automatic saving of runs as organized, reopenable, shareable files. Update to 0.5.35, stack a few pairs into Multi-Backtest, and click Run All.

Join the Waitlist

Until now, a backtest on KryllOS ran on a single core, and only one at a time. No matter how many cores were available on your machine, it was impossible to launch a second one while the first was running. 0.5.32 changes that in a fundamental way: backtests can now run across multiple cores in parallel, so you can launch several at once. This release also brings better tracking and better RAM management.

Parallel backtests

With 0.5.32, you can finally run several backtests at the same time, each on its own core. Where you used to have to wait for one backtest to finish before starting the next, you can now open several tabs and run them simultaneously, a real time-saver when you're testing multiple versions of a strategy or several pairs in parallel.

Configuring allocated power

How many backtests you can actually run at once depends on the power of your machine, and more specifically on the number of cores available on your VPS. To make the most of it, head to Settings > Performance, under "Parallel backtests," where two sliders give you control over this allocation.

• Backtest engines: the number of active engines running in parallel, each on its own core. This is the real speed lever, more engines means more backtests moving at full speed at the same time. KryllOS automatically detects your available cores and recommends a value suited to your machine (it always keeps some in reserve for your live trading).
• Multiplexed slots: several backtests sharing a single engine, each taking its turn. They all progress "at the same time," but none of them runs any faster than if it were running alone, the total time for the batch stays the same, it's just split between them. The point isn't speed but convenience, launching a whole batch of backtests at once, without waiting for each one to finish before moving to the next.

The total number of backtests you can launch follows the formula shown at the top of the panel: engines × slots. The panel also displays an estimate of the RAM required.

How to set up your parallel backtests

• Open Settings,then Performance
• Increase Backtest engines for real speed, within the recommended limit for your machine
• Increase Multiplexed slots to move several backtests forward per engine, with no speed gain
• Click Apply

*Reducing the number of engines never interrupts a backtest that's already running.

RAM under control

The second panel, Settings > Memory, gives you visibility into what KryllOS is actually consuming. You can see memory usage, engine by engine, and an alert warns you in real time when RAM or disk usage climbs too high.

KryllOS keeps candles and indicators in memory from one backtest to the next to stay fast, instead of reloading everything each time. That's a good trade-off, but over a long session, this memory builds up. KryllOS already cleans it up automatically past a certain threshold. And to take back control immediately, a "Clear RAM" button frees up memory on demand.

This cleanup never touches a backtest that's currently running. It only clears stopped engines. If two backtests are running, Clear RAM leaves them alone. If you stop one and then clean up, only that one gets cleared. If you restart it afterward, the data reloads and memory goes back up, that's normal, it's the cache doing its job again.

Strategy logs, on demand

Still in the Performance panel, a useful setting: "Emit strategy logs." When enabled, KryllOS produces server-side logs. This is useful when an indicator isn't doing what you expect and you want to see, step by step, exactly when it's waiting and when it triggers.

When disabled, no lines are produced, not in memory, not in the stream, not on disk, and your backtest runs a bit lighter without that writing overhead. Turn it on when you're debugging, turn it off when you want to optimize for speed.

A backtest engine that cleans up after itself

These settings hold up thanks to background work on the engine's memory consumption.

First, a new way of reading market data, organized in columns, which lowers a backtest's peak memory usage by about 36%. Each backtest leaves more room for the others, which means more of them can run before the machine gets saturated.

Next, engines no longer hold onto RAM when they're not in use. An idle engine frees its memory and shuts down automatically, then powers back up on demand as soon as a backtest is restarted. Memory is only consumed by what's actually working.

Finally, a backtest's results are no longer kept in memory once the run is finished. They're released, and to export them, KryllOS reads them back from disk.

0.5.32 brings two things: real backtest parallelism, and visibility into RAM. Update to 0.5.32, take a look through Performance and Memory, then launch two backtests at once to see the difference.

Join the Waitlist

Building a strategy is often a loop: you set a block, adjust a level, move a condition, and after every change the same question comes back, does it hold up? So you run a backtest, to ask the market's past what it thinks.

The problem is that every backtest has a cost in time. When waiting for a result takes several minutes, you become frugal: you only test the ideas you're already fairly sure about, and all the "what if I tried this" thoughts stay in a corner of your mind, never checked. Every one of those untested variants is a path you'll never actually know.

0.5.29 shifts that balance. As of this KryllOS version, backtests run much faster, fast enough that testing one more idea costs almost nothing, so there's no real reason to hold back anymore.

The waiting wall comes down

KryllOS's backtesting engine was already fast: it ran 2 to 10 times faster than the old engine. 0.5.29 adds up to another 4x on top of that. Long periods that used to take several minutes now run in seconds, and you can chain tests together without losing track of what you set out to check.

The cache that makes technical analysis free

Where does this speed come from? Largely from a cache, a memory the engine builds up across runs so it never has to redo the same work twice.

Specifically, two things now persist from one backtest to the next. Candles, first: the engine no longer has to fetch them from disk on every run, it keeps them on hand. Your indicators, second: your RSI, your moving averages, your Supertrend are no longer recalculated every time, they're computed once and reused.

The result: after the first pass, your technical analysis costs your machine almost nothing. The engine no longer spends its time rebuilding your indicators; it spends it replaying prices and measuring how your strategy behaves.

That's also why the very first run is a bit slower than the ones that follow: it's the one filling the cache. If your first backtest isn't instant, that's normal. Run it again, and you'll feel the difference.

Dead time, compressed

Speed doesn't only come from the cache. The way the engine replays the market has changed too.

A market doesn't move at a steady pace: there are moments when everything moves, and long stretches where nothing happens. Before, the engine still advanced step by step through those quiet stretches. Now, it crosses them in one go: uneventful ticks are compressed, candles that don't change anything for your strategy are skipped, and the engine jumps straight to the next event that actually matters to you.

It's a bit like fast-forwarding through the boring parts, with a return to normal speed only where something is really happening.

Precision: your cursor between speed and detail

You can dial in this speed yourself with a setting in the top bar of the editor, just to the left of the Run button: Precision.

Precision defines the number of ticks the engine generates inside the candles, in other words, how finely it emulates price movement inside each candle. The lower you set it, the fewer points to simulate, the faster it runs; at 0, you're at maximum speed. The higher you set it, the more detail the engine works out inside each trade.

This mainly affects your stop losses and your trailing orders: the exact point where the price passes inside the candle decides the moment your order triggers. On a simple strategy, though, your P&L barely moves between a precision of 0 and 4.

In practice: lower the precision to prototype and chain through tests quickly, raise it back up when you want an accurate read on your stops and trailing orders before going live.

KryllOS Onboarding: A Warm Welcome to Get You Started

KryllOS now takes care of your very first minutes. The first time you launch the app, a quick welcome tour walks you through the essentials in five screens: what KryllOS is and what it gives you, your VPS profiles, the toolbar you summon with F10, and where to drop us a bug or an idea. No more being thrown in at the deep end, you know where to put your hands from the very first launch.

Join the Waitlist

In front of a chart, your eye never rests on price alone. It hunts for the moving average carrying the trend, the RSI starting to lose steam, or any other indicator traders swear by. Laid over the candles, they're what turn a column of numbers into a market you can actually read.

Except that, until now, the KryllOS editor's chart showed price, candles and volume, nothing more. Your indicators, meanwhile, ran inside your blocks without ever showing up on the candles.

That's over now. As of KryllOS 0.5.26, technical indicators appear directly on your editor's chart, right there among the candles, while your strategy takes shape.

The resizable chart

You could already open and collapse the chart above your strategy. What's new is that it now comes in two sizes. First a compact one, which leaves you enough room to keep wiring your blocks while keeping price in view. And a large one, which unfolds the chart and gives it more space for a real analysis session.

• Compact mode: you edit your blocks, the chart stays visible
• Expanded mode: a bigger chart, room for analysis
• Switch modes in one click

How to do it

1. Find the double chevron ⩔ in the center, right at the bottom of the chart
2. One click to expand it, another to go back to compact

Adding indicators

To add one, right-click on the chart and the list opens. You browse what's available or type its name to find it right away, you click, and it settles onto your candles. Nothing stops you from stacking several: a short moving average and a long one to watch for a cross, an RSI just below, a Supertrend over the price. The more you add, the more the chart's expanded mode becomes your friend.

• Search by name to go straight to it
• As many indicators as you want, stacked on the price
• Available indicators: Moving Average, RSI, MACD, Bollinger, Stochastic RSI, Supertrend, Ichimoku, Volume

How to do it

1. Right-click anywhere on the chart
2. In the list that opens, pick an indicator or type its name in the search
3. Click it, and it drops onto the price
4. Repeat to stack more

Managing and cleaning up your indicators

A busy chart needs a bit of tidying. You can hide an indicator to get it out of view without losing it, then bring it back the moment you need it again. You can also delete just one, the one you no longer need. And the day you want to start from a blank canvas, there's no need to remove them one by one: right-click the chart, choose to remove them all, and every indicator disappears at once. Two clicks, and you're starting fresh.

• Hide / show an indicator without losing it
• Delete a specific indicator
• Remove them all at once: right-click, then "remove all indicators"

How to hide an indicator

1. Hover over its name, at the top left of the chart
2. Click the ◉ icon to hide it. Click again to bring it back

How to remove all indicators

1. Right-click on the chart
2. Click "remove all indicators". They all disappear at once

Customizing each indicator

Each indicator opens onto its own settings panel, and you really can tweak all of it. You lengthen or shorten its period to set it anywhere from short term to very long term, you switch its calculation method when it offers several, you adjust the line thickness and its color, and you even choose the price source it works from, whether it starts from the close, the open, or one of the classic combinations traders are used to. Nothing is set in stone. You set up each indicator exactly the way you read it in your head, with your own reference points and your own way of trading.

How to do it

1. Hover over the indicator and click the gear ⚙
2. Adjust whatever you want in the panel (period, style, color, source...)
3. Changes apply directly on the chart

Reading values on hover

Move your mouse over the chart and your indicators hand you their numbers. A dot snaps onto the curve, and its exact value appears off to the side, at the precise moment you care about. Enough to read the value of your moving average or your Supertrend down to the exact candle, without ever drowning the chart in numbers.

How to do it

1. Move your cursor over the chart
2. Each indicator's value appears at the point you're hovering over

In the end, all these settings and shortcuts come down to one simple idea: your technical analysis and your strategy now live in the same space. And that's the whole point: you no longer build your strategy by imagining what your indicators are doing, you build it from what you see. The rest is yours to write. Update to 0.5.26, open your editor, and drop your first indicator onto the price ;)

Join the Waitlist

KryllOS is a self-hosted product: you install it on your own server, and you are its sole user. No Kryll cloud holding your keys, no account to create, no password to manage.

This reality fundamentally changes the nature of the security model. The question is no longer "how to protect a multi-tenant service," but "how to protect a personal server that has no reason to be accessible from the outside." KryllOS's model responds with a simple principle: robust where it matters, lean where it's enough.

A solid security boundary

KryllOS is only accessible by you, via an SSH tunnel whose port remains permanently closed. It only opens after a port knocking sequence known to you alone. To an attacker scanning the Internet, your server doesn't exist: no open ports, no response, no visible attack surface.

This invisible-before-authentication approach applies a model designed in 2007 by the Defense Information Systems Agency (DISA) of the U.S. Department of Defense. Known as Software Defined Perimeter, or "Black Cloud," it was originally conceived to protect classified networks. It is today the foundation of Zero Trust architectures powering Cloudflare Access, Zscaler Private Access, and most modern ZTNA solutions.

No unnecessary friction between you and yourself

With a solid perimeter in place, the protections typically layered on the inside — HTTP authentication, sessions, rate limiting, local encryption of secrets — lose their purpose. If someone has crossed the SSH tunnel, it means they have your keys or a shell on your machine: from the system's perspective, they are you. Encrypting an API key with a decryption key stored right next to it doesn't change the cost of an attack.

KryllOS therefore chooses to be honest about what it actually protects, and to focus cryptography where it truly matters.

Cryptographic guarantees where they count

• Signed plugins: cryptographic signature verified before each execution, with auditing for the official marketplace.
• Sandboxed filesystem: all file operations pass through a validation layer that prevents a plugin or API call from escaping its dedicated folder.
• Hash-pinned dependencies: KryllOS and its components are distributed with a cryptographic manifest that allows verification that downloaded third-party libraries are exactly those tested by the team. A compromise of PyPI or an upstream repository cannot silently slip into an update.
• Isolated exchange credentials: your API keys are stored in a local SQLite database, accessible only by the KryllOS process itself.

Best practices on the user side

KryllOS handles what it can handle. The rest comes down to a few classic administration best practices:

• A strong SSH key (Ed25519, never passwordless) with a local passphrase.
• A port knocking sequence you don't share, and that you change if it has leaked.
• Exchange API keys created with minimal permissions (trading only, no fund withdrawal, IP restriction where the exchange allows it).
• Extra vigilance with plugins installed outside the marketplace: a third-party plugin is code that runs with your server's privileges. The official marketplace exists precisely so you don't have to do that analysis yourself.

A model suited to its audience

This isn't Binance or Coinbase. KryllOS doesn't hold the funds of millions of users, isn't publicly exposed on the Internet, has no attack surface to defend against continuously scanning bots. It's a personal trading station that, from the Internet, simply doesn't exist.

At this scale, the challenge isn't to build a defensive fortress. It's to shrink the attack surface until it becomes invisible, and to focus cryptography on the points that remain.

Join the Waitlist

KryllOS is more than an automated trading platform. It's an ecosystem: a visual no-code editor, a marketplace for bots and custom blocks, an AI layer for vibe-coding your strategies, and at the heart of it all, a token that serves as the economic backbone. KRL isn't a gimmick, it's the economic fuel that aligns users, creators, and the platform.

Token Basics

KRL is the native utility token of the Kryll ecosystem. Launched via ICO in early 2018, it raised $2.2M and laid the project's foundations. Eight years later, it's back at the center of the action with KryllOS.

A few fundamentals to keep in mind:

• Standard: ERC-20
• Max supply: 49,417,348 KRL
• Multi-chain: natively deployed on Ethereum, Base, Arbitrum, and Optimism
• Availability: traded on Coinbase, KuCoin, Gate.io, Crypto.com, MEXC, CoinEx, and accessible on DEX via Uniswap V3

One important point: all KRL currently in circulation is fully unlocked. There is no active vesting, no upcoming unlock schedule. The supply is fixed and non-mintable, a clean, predictable foundation for everything that follows.

The Marketplace's Single Currency

Every transaction on the KryllOS marketplace is designed to go through KRL. Whether you're buying a ready-to-use trading strategy, a custom block, an app, or a skill for your AI agent, you pay in KRL. The publisher receives KRL.

No fiat, no stablecoins, no alternatives. A single rail, simple and predictable. This unification has a direct consequence: every transaction feeds the same economy. The more volume the marketplace generates, the more sustained demand builds around KRL.

How a Single Purchase Powers an Entire Ecosystem

With every marketplace purchase, the KRL spent is distributed among three beneficiaries:

• The Publisher
  The creator of the bot, block, or application receives their share. This is the foundation of a real creator economy: the more useful content you publish and the more it gets used, the more you earn. The original Kryll marketplace already proved this model works, top creators generated genuine passive income from it. KryllOS takes that further, adding custom blocks and an AI layer that dramatically lowers the barrier to publishing.
• Kryll
  A share goes to the team to fund development, infrastructure, and operations. This is what keeps the product free: no subscriptions, no trading fees, no custody. The marketplace funds the platform instead of billing the end user.
• Stakers
  A share is redistributed to holders who have actively staked their KRL, in the form of real yield paid out by actual marketplace activity. This is an intentional, participatory mechanism: simply holding KRL in a wallet doesn't earn you anything. It's the deliberate act of staking that opts you into the revenue-sharing engine.

Real Yield, Not Disguised Inflation

The word "yield" is overused in crypto. Most projects that promise it operate through inflationary emission: new tokens are minted to pay stakers. The result is that non-staking holders get diluted, and the displayed APY reflects no real value creation.

KRL works in the opposite direction. The supply is fixed: 49,417,348 tokens, full stop, no minting possible. The yield distributed to stakers doesn't come from emission, it comes from real purchases made on the marketplace by real users. It's closer to a corporate dividend than a synthetic APY.

In practice: the yield is sustainable because it's backed by actual economic activity. And staking holders capture their share without diluting those who don't stake.

A path worth considering: Burn & Buyback
A portion of the KRL collected through the marketplace could be burned, mechanically reducing the circulating supply. Additionally, in cases where the platform generates revenue in fiat or currencies other than KRL, a buyback mechanism could be considered, repurchasing KRL on the open market to redistribute or burn it, creating structural buying pressure on the token.

Publication Collateral

For a marketplace to stay healthy, publishers need a direct incentive to be serious. One option being strongly considered: requiring a KRL deposit as collateral in order to publish on the marketplace.

This collateral would serve as an integrity guarantee, a publisher who releases defective or fraudulent content loses all or part of their deposit. Conversely, an active and honest publisher sees their collateral grow over time, with a portion of their earnings automatically reinvested into it.

When a publisher decides to leave the ecosystem, they recover their full accumulated collateral. It's a mechanic that creates genuine long-term stakes without imposing excessive friction at the point of entry.

The Self-Reinforcing Loop

Put together, these mechanics create a virtuous cycle, a flywheel, that strengthens itself over time.

More users on KryllOS → More marketplace volume → More buying pressure on KRL → Greater attractiveness and visibility → Repeat

Every participant benefits from everyone else's success. Users want a rich marketplace. Creators want a large user base. Stakers want both sides of the market to grow. And Kryll, as the platform, lives off the same flow. Nobody is playing against anyone else, the exact opposite of classic SaaS models where the platform extracts rent at users' expense.

What KRL Makes Possible That Nothing Else Could Fund

Kryll makes strong product choices that set it apart: open source, self-hostable, free, non-custodial. Kryll never touches user funds and takes nothing from their trades. No subscriptions, no paywalls, no friction.

In that context, one might wonder why have a token at all. The answer comes down to one word: alignment.

With KRL, the ecosystem finances its own growth. The platform stays free because the marketplace funds development. Creators earn a living because users buy their work. And holders who believe in the project capture a direct share through real yield.

KRL isn't a financial layer bolted onto the product. It's what makes the product possible in its current form: open, free, sovereign, and viable for the long term.

Join the Waitlist

Self-hosting has a beautiful promise: your keys, your data, your rules. And it comes with a very real price. You need to configure a VPS, properly set up an SSH tunnel, navigate Linux command lines, and make a series of configuration decisions without making mistakes, all while carrying the nagging anxiety of breaking something along the way. This is often where the promise meets reality.

When preparing the reboot of Kryll, we asked the community directly. 58% said they were ready to self-host their instance, provided they had guidance. In other words, for nearly six out of ten people, the installation process was not just a technical step.

The KryllOS installer was designed exactly for these people. Three steps. Five minutes. A fully operational instance, already secured.

Why an installation wizard for a self-hosted trading bot?

KryllOS is deliberately self-hosted. Your API keys stay on your machine, your trading data never leaves to any third-party cloud, and nobody holds custody of your funds. It's a choice of total sovereignty, but it's also a choice that traditionally requires users to have some technical knowledge.

We refuse that compromise. The idea behind KryllOS is the power of a professional tool with the simplicity of a consumer app. The installation wizard embodies exactly this philosophy: it automates what an experienced sysadmin would do by hand, and it does it better than a copy-pasted tutorial, because it bakes in security best practices by default.

Concretely, the KryllOS installer handles three tasks for you:

• SSH connection to your VPS (no more juggling your terminal and private key)
• Security hardening, with the creation of a dedicated Linux user, firewall configuration, and remote connection rules, plus, optionally, port-knocking
• Deployment of KryllOS on your VPS and configuration of the KryllOS app on your computer

You click three times, wait five minutes, and you trade.

The 3 steps of the KryllOS wizard

Step 1: Connect your VPS to KryllOS

On the first screen, the wizard asks for three pieces of information:

• Your VPS IP address
• The root password for that VPS
• A username to create for KryllOS

The choice to create a dedicated user, rather than running KryllOS with root privileges, is not a minor detail. It's the principle of least privilege: even in the unlikely scenario where a vulnerability were to affect the application, the attacker would find themselves confined to an account with limited rights, far from the absolute power that root provides.

Step 2: Choose your installation mode: Native or Docker

The KryllOS installer offers two installation options:

• Native installation: if your VPS is dedicated to KryllOS, this is the simplest and most direct choice. KryllOS installs directly on the system, without any additional layer.
• Dockerized installation: this is the option for advanced users who already have an active VPS running other services. Think of Docker as a sealed box sitting on your server. KryllOS runs inside it, completely isolated from the rest of the system. No conflicts with your other software, no interference in either direction.

On this same screen, you'll find a checkbox that may look minor but is worth its weight in gold: port-knocking.

Port-knocking, or the art of making your server invisible

Port-knocking is a somewhat forgotten but diabolically effective security mechanism. It makes your server completely invisible, no ports are open. To an automated scanner looking for vulnerable VPS machines, your server simply doesn't exist.

But how does it actually work?
Picture a secret door in a wall that, on the surface, has no visible entrance. For the door to open, you must knock in a precise sequence: three times, then twice, then five times. Anyone who doesn't know the code sees nothing but a smooth wall.

Port-knocking works on exactly this principle. A server has thousands of "doors" called ports, and connections pass through these ports. Normally, certain ports remain permanently open, like the SSH port, which enables remote connections. These open ports are precisely what hackers and their bots scan relentlessly, looking for a vulnerability.

With port-knocking, no port is open by default. Instead, the server quietly listens for connection attempts on a specific sequence of ports, say, 1200, then 3456, then 7890, in the right order and within a limited timeframe. This sequence is the "secret knock." If you know it and send it correctly, the server dynamically opens the SSH port, just long enough for your connection, then closes it immediately. To everyone else, the door never existed.

How can a hacker compromise a machine that doesn't even appear to exist from their perspective? That's exactly the point. KryllOS already stacks several security layers, dedicated user, Docker isolation, hardened SSH, and port-knocking adds the final touch: an invisibility layer. One checkbox, and your VPS disappears from the map.

Step 3: Summary and deployment

The final screen summarizes all the choices you've made. You review them, click deploy, and the installer takes over.

Behind the scenes, it runs through a precise sequence:

1. Secure connection to the VPS
2. System compatibility check
3. Environment configuration
4. KryllOS installation
5. Final checks to ensure everything is running correctly

In under five minutes, KryllOS is up and running. The application is directly accessible on your local machine, already connected to your VPS.

What remains in your hands after installation

The installation ends, and you find yourself with far more than a simple configured instance. Behind the scenes, the wizard has been running two parallel workstreams.

On one side, on your VPS: KryllOS is deployed, the server is hardened, the environment is isolated, and your API keys will never leave that machine.

On the other side, on your computer: the KryllOS application has been configured locally. This becomes your control station. It establishes a secure SSH tunnel to your VPS and gives you access to the full KryllOS interface from a native app, without ever going through a browser or a third-party service. The VPS runs the engine. The application on your machine holds the wheel.

The old crypto adage "not your keys, not your coins" extends here to automated trading. Your strategies run on your machine, for you. And your only point of contact with all of this is an interface built to be used, not feared.

Join the Waitlist

KryllOS without its Marketplace would be like a Mac without the App Store: powerful, but limited to what was originally designed and shipped. An OS that can't expand after launch is an OS that stagnates. The Marketplace is what turns KryllOS into a living platform, an ecosystem that grows continuously through community contributions, not just the decisions of a central product team.

Why a marketplace in an OS

Kryll isn't a website with menus and pages. It's a multi-window, modular, self-hosted OS running on your VPS. Instead of being stuck with features hard-coded by a distant product team, you compose your own automated trading environment yourself.

And where there's an OS, there's a store. The Marketplace is the nerve center where everything converges: one place, one currency, one unified experience, whether you're looking for a complete strategy, a custom editor block, an app, or a skill for your AI agent.

One number that says it all: in the community survey run before launch, 58% of respondents said they prefer downloading ready-to-use strategies rather than building them from scratch. The Marketplace isn't a nice-to-have, it's a core need.

What you can download

Four content categories, from the most plug-and-play to the most advanced.

Complete trading strategies: download a bot, connect your exchange, hit go. No need to touch the editor. Perfect if you don't have time to build from scratch, or if you want to learn from someone better than you. And since Kryll is open source, these strategies aren't black boxes, you can open them, dissect them, fork them. The Marketplace becomes a learning ground too.

Custom editor blocks: building your own strategies but want superpowers? An exotic indicator, advanced logic, a connector to a third-party API. Install it, and the block appears in your library just like a native block.

KryllOS apps: one level up, these aren't editor building blocks, they're OS extensions. Custom dashboards, market scanners, trading journals, external integrations. Each app opens in its own window, right alongside your editor or performance tracker. This is what takes Kryll beyond "bot factory" and into a full trading suite.

Agent skills: the augmented AI layer to extend your agent's action capabilities. Every installed skill becomes a permanent capability of your agent, activatable on demand.

For creators: a wider playing field, an audience already there

Everything above was about what you can download. The other side of the Marketplace is what you can sell.

If you can design a strategy that holds up, build a block others would kill to have, or imagine an app that changes a trader's daily workflow, your expertise becomes a monetizable asset, paid in KRL with every sale.

Three reasons to go for it now:

• Four surfaces instead of one: Strategies, custom blocks, apps, agent skills. Whatever your profile, trader, dev, crypto ops, there's a category where what you already know how to do has real value, without switching careers.
• The audience is already there: The majority of KryllOS users arrive with the explicit intent to consume community content. No need to build an audience before you sell, just be good and visible in the store.
• Publishing is more accessible than anywhere else: KryllOS is open source and self-hosted: no proprietary stack to master, no app review, no gatekeeper. You build with the same tools as your future customers, and you publish.

The economic engine: triple split and flywheel

The Marketplace runs on a single currency: KRL, Kryll's native ecosystem token. Complete strategy, editor block, KryllOS app, or agent skill, everything bought in the store is settled in KRL. This unifies the buying experience for users, and directly connects the Marketplace to the rest of the tokenomics.

When a purchase is made, the KRL is split three ways.

• The publisher gets their cut, making quality content creation economically viable and keeping the best creators motivated to keep producing.
• Kryll takes a commission that funds product development, infrastructure, and operations.
• KRL stakers receive a redistribution: this is the real yield mechanism. Staking KRL earns you a share of Marketplace volume, generated by real economic activity, not token inflation.

The Marketplace isn't a module sitting beside the Kryll product. It's the engine that turns an automated trading OS into a complete ecosystem, one that grows every day from what its community brings to it.

Whether you're here to download and run your bots without reinventing the wheel, or to publish your work and build a passive income stream in KRL, the Marketplace is probably your first entry point into KryllOS. And it might just be the reflex worth building: before opening the editor to a blank page, go see what the community has already put on the table.

Join the Waitlist

Before risking capital on a strategy, you test it on historical data. That's the principle behind backtesting. Simple in concept, but the quality of the results depends entirely on the tool you use.

In KryllOS, we rebuilt the engine from the ground up. Here's what that means.

More accurate. And much faster.

The new backtest engine uses a 16-tick-per-candle interpolation system that produces results significantly closer to what would happen in live trading.

But accuracy is only half the story. The other half is speed. The new engine is radically faster than the old one. That speed gain genuinely changes the way you work: you iterate more, test more, validate faster.

Run multiple backtests at the same time

With MultiBT, you no longer run backtests one after another. You run them all at once.

This opens up concrete possibilities: testing a strategy across multiple time periods to verify it holds up over time, validating it on several pairs or assets simultaneously, or comparing multiple configurations of the same system in a single run.

What used to take an hour of sequential testing now runs in parallel. More comparisons, in less time, with a far more complete picture of what your strategy is actually worth.

Your backtests stay with you

KryllOS is self-hosted. Backtests run entirely on your machine, and no data leaves it, not your strategies, not your results, not the pairs you're testing. On a cloud platform, you're entrusting your ideas to a third party. With KryllOS, they truly belong to you.

An engine you can read

KryllOS is open source. The backtest engine is too. You can read exactly how the calculations are made, verify the interpolation logic, and make sure there are no hidden biases in the results.

In a field where trust in the tool matters as much as the tool itself, that's far from a minor detail.

Join the Waitlist

In recent years, one concept has completely changed the way we create with AI: vibe coding. You describe what you want, and the AI builds it. You don't write code, you express an intention. In most tools, this generates code. In KryllOS, it lets you create trading strategies, editor blocks, and entire applications.

Creating and modifying a trading strategy

In KryllOS, AI isn't integrated separately into each application. It's a standalone app at the system level, capable of interacting with everything you're working on.

Open the strategy editor, and the AI can act on it directly. Describe the logic of the trading bot you want to create, and the AI places the blocks and connects them.

Want to modify an existing strategy? It touches what needs to be touched, nothing more. Feel like exploring an idea before building? It brainstorms with you, then waits for your approval before creating anything.

Anyone who's spent hours wiring blocks by hand knows exactly what this changes.

Auditing before deploying

Building fast is easy. Building right is another matter.

KryllOS's AI can read a strategy and surface issues that a classic backtest might miss. A backtest only detects a design flaw if the conditions to trigger it occur during the tested period. The AI reads the logic directly: it identifies flow freezes, dead branches, conditions that are never met, loops with no exit, without waiting for the market to trigger them.

It also simulates scenarios nobody thinks to test: flash crashes, zero volume, flat markets lasting weeks. And it verifies that the strategy actually does what you think it does. That's usually where the surprises come in.

Creating your own blocks

KryllOS lets you create your own editor blocks and add them to your library as if they were native. You can download them from the marketplace, or create them via AI. A few examples of what this enables:

• Adding natively absent indicators: VWAP, CVD, Pivot Points, Futures Funding Rate.
• Encapsulated logic: a "market regime" block that detects trend/range/volatility and outputs a binary signal. A "trading session" block aligned with London or New York opening hours.
• External data: a TradingView signal via webhook, a sentiment API, an on-chain condition before each entry.

Once created, the block behaves exactly like a native block in KryllOS. And it can be shared or sold on the marketplace.

Creating KryllOS applications

KryllOS is a true OS: it supports third-party applications with a signing system, just like a classic operating system. If a native app doesn't do what you want, you build another one. With vibe coding, this promise becomes concrete. Here's what you can build:

• Alerts and notifications: an app that sends a Telegram message when a bot hits a profit threshold or when a trade closes.
• Market data: a real-time screener, an on-chain/DeFi aggregator, a multi-exchange funding rate tracker.
• Orchestration: an app that dynamically allocates capital across your bots based on their performance, or that activates/deactivates strategies based on market conditions.
• Reporting: an automated trading journal, an export to your own tools, a weekly report generated without lifting a finger.

We pushed the concept so far that our developers had fun building a Doom app. Perfect for unwinding between two backtests 😎

KryllOS in your pocket, via Telegram

KryllOS runs on your VPS, but that doesn't mean you need to be at your desk to control it. Thanks to the Telegram integration, you stay in control of everything, wherever you are.

From a simple conversation, you can remotely start or stop a strategy, check your bots' performance in real time, and receive instant alerts when a trade triggers or a profit threshold is reached.

One message is all it takes to activate a strategy, pause another, or check the status of your portfolio. It's your dashboard in your pocket.

Your OS. Your playground.

KryllOS belongs to you, in the most concrete sense of the word. It runs on your VPS, your data never leaves your environment, and you can truly make it whatever you want.

Everything you create, whether a strategy, a custom block, or an application, can stay private or join the marketplace for others to benefit from. That's how the ecosystem is built.

The possibilities are endless. The only limit is your imagination, and we can't wait to see what you'll create!

Join the Waitlist

The word "free" has been so badly abused in the trading industry that it has almost lost all meaning. Behind the label, you'll typically find a fourteen-day trial, a version stripped of its useful features, a percentage taken from each transaction, or a subscription that appears at the exact moment the tool starts being useful to you.

Kryll follows none of these patterns. What you download is the complete version of the product, with no deferred strings attached.

What the product doesn't include

Kryll has no subscription screen. It also has no pricing grid, no trial period, and no feature locked behind an "upgrade to a higher plan" button. The number of bots you can run is subject to no cap, nor is the complexity of your strategies, and no commission is taken on your transactions. Your bank card will never come into play.

The practical consequences

A tool that costs nothing radically changes the way you use it. The small mental profitability calculations you run before every decision disappear, and several uses become possible that weren't really viable with a monthly subscription in mind.

Testing a strategy idea on a small amount of capital, for example, stops being pointless. Running eight bots in parallel to compare their behavior costs no more than running just one. And nothing stops you from setting the tool aside for six months, long enough for a market cycle to feel readable again, then picking up exactly where you left off. No invoice will have arrived in the meantime.

A matter of structure, not commercial policy

This point is worth clarifying, because it is often misunderstood: the absence of fees on your trades is not a marketing promise. It stems from the way Kryll is built.

The software runs on your machine. Your API keys stay there. Your capital never passes through our servers at any point, and we have no access to your funds. Charging a commission on your transactions would be technically impossible for us. The profits generated by a strategy therefore come back to you in full, and this doesn't depend on any decision on our part, it is the product's architecture that guarantees it.

Open source as a safety net

If Kryll is entirely free, the explanation also lies in its open-source nature. A public, auditable, and freely modifiable codebase does not give its authors the option of deciding, one morning, that access to the software will become paid. The switch would be theoretically possible, but it would immediately give way to a community-maintained fork. That prospect alone is enough to make the idea unattractive.

Kryll is therefore not merely a product made available to you. It is, to a certain extent, a product that belongs to you.

Frequently asked questions

A few questions come up regularly enough to be worth addressing.

• "Is a subscription planned down the line?"No. Neither the project's business model nor its architecture provide for one, and the open-source nature makes the scenario unconvincing.
• "Is the free version limited?"No. All features are present from the very first launch.
• "Where's the catch?"There isn't one ;)

Zero at installation, zero per month, zero on your trades. Kryll, in all of this, is simply the engine that keeps everything running.

Join the Waitlist