Cloud and in-browser Kiri:Moto

Use Kiri:Moto online - in our cloud, or on your own machine

Core Slicing Free plan

Use Kiri:Moto in your browser or through SimplyPrint's cloud, including native slicing for continuous-belt printers.

View Slicer overview Get started for free
Feature image

What is Kiri:Moto?

Kiri:Moto is an open-source 3D printing slicer written by Stewart Allen at Grid.Space. Where most slicers are desktop applications that were later wrapped for the web, Kiri:Moto was built to run in a browser from the beginning - and it slices for continuous-belt printers natively, which almost nothing else in the FDM world does.

On SimplyPrint it is one of 7 slicing engines sitting behind one web interface. You pick the engine, we hand it the plate, and your files, profiles, print queue and printers stay exactly where they were. Switching engine is a dropdown, not a migration.

It is also the only one of those engines whose slicing can run on your own machine instead of ours.

We currently run version 4.7.1, released June 22, 2026, and the engine's own documentation lives at docs.grid.space.

Slice locally, in your own browser

The only engine that never has to touch our servers

Open the slicer, pick Kiri:Moto, and the engine picker offers a second option next to the cloud: Local - "slice in this browser using the local runtime". Choose it and the Kiri:Moto runtime loads into the page and turns your plate into G-code on your own processor instead of ours.

Why you might want the local option:

  • The slicing step stays on your machine. Your geometry is not handed to a slicing server to be turned into G-code - the browser tab does it.
  • It runs on your hardware, not shared hardware. A local slice uses your own processor, so how fast it finishes is up to your machine rather than to how busy our slicing capacity is.
  • It is still the same account. The resulting G-code saves, queues and prints exactly like a cloud slice, because only the slicing step moved.
And when the browser runs out of room, switch back to Cloud. A browser tab only ever gets a slice of one machine, and it has a hard memory ceiling it cannot be argued out of - feed it a big enough model and the slice crawls, or the tab simply gives up with an out-of-memory error. Our slicing servers have neither limit. Same engine, same version, same settings, same result: pick Cloud for the plate the browser cannot finish, and we remember your last choice per engine.

That difference is also why they are priced differently. Local slicing is free and unlimited - it runs on your processor, so there is nothing for us to meter. Cloud slicing draws on your plan's monthly allowance, because it runs on hardware we pay for.

Feature image

So why slice with Kiri:Moto through SimplyPrint?

Most slicers we support are desktop applications, so putting them in a browser is genuinely the thing SimplyPrint adds. Kiri:Moto is the exception: it has run in a browser since the day Stewart Allen wrote it, and you can use it right now at grid.space without an account, without us, and without anyone's servers. Being able to reach it from an iPad is not something we invented and we will not pretend otherwise.

What you get here is everything on either side of the slice:

  • Your printers are already connected. The G-code does not get downloaded and carried anywhere - it lands in your file library and goes straight to a machine, or into the queue.
  • One interface, whichever engine suits the printer. If you run a belt printer and a multi-colour machine side by side, Kiri:Moto slices the first and OrcaSlicer the second - same files, same account, a dropdown apart.
  • More room than a browser tab has. When a model is too heavy to slice locally, the cloud option takes it without you switching tools.
  • And local slicing stays free. No limit, no plan gate, no counter - it runs on your machine, so charging for it would be charging for nothing.
Some people will say that running Kiri:Moto in a cloud rather misses its point. They may well be right - and if slicing on your own machine is what you value about it, grid.space is where to do it, with our blessing. We offer the engine because some of our users want their belt printer and their Bambu in one place, not because we think we improved on it.

How Kiri:Moto compares with our other engines

Every engine we support is good at something different, and Kiri:Moto is the specialist. This table is generated from our own slicer, so it says what each engine can do through SimplyPrint today - which, for the last two columns, is not always the same as what the engine can do on its own:

EngineWhere slicing runsBelt printersMulti-extruder plates (via us)Per-object settings (via us)
PrusaSlicerOur cloudNoNoNo
OrcaSlicerOur cloudNoYesYes
BambuStudioOur cloudNoYesYes
ElegooSlicerOur cloudNoYesYes
CrealityPrintOur cloudNoYesYes
CuraOur cloudNoNoNo
Kiri:MotoOur cloud, or your own browserYesNoNo

Read it as a division of labour rather than a ranking. Kiri:Moto is what you want for a belt printer, or for slicing on your own machine; OrcaSlicer, BambuStudio, ElegooSlicer and CrealityPrint are what you want for a multi-colour plate.

Feature image

Native slicing for continuous-belt printers

Infinite Z, without a patched slicer

A belt printer has no fixed-height bed. The print surface is an angled conveyor, so the Z axis is effectively endless and a finished part rolls off the end while the machine keeps going. That geometry needs a slicer that understands it, and most do not.

Kiri:Moto does, and it is the only engine on SimplyPrint that does. Select a belt printer and the build area reports an unlimited Z and extends along the belt as you add parts; slice with Kiri:Moto and the G-code comes out in the belt's own angled coordinate system, with the anchor and lead-in a belt print needs - in the same interface you use for every other machine in the account.

Combine that with AutoPrint and the queue empties itself: because the part clears the bed on its own, there is no clearing routine to run between jobs and no one has to be there.

See how belt printers run unattended

What Kiri:Moto will not do, and what to use instead

Three things you cannot do with Kiri:Moto on SimplyPrint today. All three are limits of our integration rather than of the engine - Kiri:Moto can do more than we currently ask of it - but they are real today, and pretending otherwise would only waste your afternoon:

  • Multi-material or multi-colour plates - through us. Kiri:Moto handles multiple extruders perfectly well on its own; what SimplyPrint cannot do yet is hand it a multi-material plate, so we refuse one rather than silently dropping a material. For an AMS, a CFS or any other filament changer, switch to OrcaSlicer, BambuStudio, ElegooSlicer or CrealityPrint.
  • Per-object settings - through us. You cannot give one model on the plate its own infill or supports, because the scene we send Kiri:Moto carries one set of settings for the whole plate. OrcaSlicer, BambuStudio, ElegooSlicer and CrealityPrint can.
  • Resin, CNC or laser. SimplyPrint is an FDM platform, so we only ever ask Kiri:Moto for FDM output.
None of that costs you anything, because the engine is a dropdown. Slice the belt job with Kiri:Moto, slice the four-colour job with OrcaSlicer, and both land in the same file library and the same queue.

What you get on each plan

Kiri:Moto itself is available on every plan, including the free one. What varies is how much cloud slicing you can do and how many profiles you can keep, since cloud slicing runs on our hardware. Slicing locally in your browser runs on yours.

Feature / Limit Free Basic Pro Print Farm Enterprise School Cloud Slicer Filament Manager
Max monthly cloud slices
How many slices per month can run on our servers 		15 15
Max slicer profiles
How many custom slicer profiles you can save to your account 		5 20 100 1000 5000 1000 50 5

Want to learn more about our plans?

View full pricing & feature comparison

Kiri:Moto is one person's work - please support it

Nearly every other slicer on this platform is funded by a printer manufacturer. Kiri:Moto is not. It is written and maintained by Stewart Allen, largely on his own, with community pull requests arriving here and there - and he gives it away. He has also helped us directly over the years - not least in getting Kiri:Moto to slice inside the browser.

If Kiri:Moto is useful to you, put something behind it: Patreon, GitHub Sponsors, or PayPal. SimplyPrint has donated to the project in the past and sent pull requests to its GitHub. If Kiri:Moto becomes something our users lean on rather than a curiosity, we will be putting more back into it - that is the honest version, and it is partly in your hands.

Kiri:Moto is also bigger than the FDM slicing we ask it for: it has SLA and CAM modes we never call, because SimplyPrint is an FDM platform. And it is not the only thing he builds - Mesh:Tool for mesh repair and editing, Void:Form for parametric CAD modelling, and Carve Control for CNC, all from the same workshop. Worth a look whether or not you ever slice anything here.

Frequently Asked Questions

Kiri:Moto is an open-source slicer built by Grid.Space, created and maintained by Stewart Allen. It was designed from the start to run inside a web browser rather than as a desktop install, and it is unusual among FDM slicers in handling continuous-belt printers natively instead of through a community patch. It was also the first slicer SimplyPrint ever shipped: from our start in 2020 until the summer of 2025 it was the only one we had, and we brought it back in the summer of 2026. It is now one of 7 slicing engines behind a single web interface.
Yes. Kiri:Moto is the only engine on SimplyPrint that offers a Local option next to the cloud one. Pick it, and the engine runtime loads into your browser and produces the G-code on your own machine, rather than sending the plate to a slicing server. Every other engine we support slices on our servers, because we run those engines as desktop binaries.
We currently run Kiri:Moto 4.7.1, released on June 22, 2026. The cloud option and the in-browser one are served the same engine version, so picking one over the other is not picking an older slicer.
Yes. It is the only one of our engines that slices for continuous-belt printers: it lays the toolpath out along the angled belt, with the anchor and lead-in a belt print needs, so a finished part rolls off the end and the next job starts behind it. Pair it with AutoPrint and a queue of jobs runs back to back with nobody touching the machine (AutoPrint and the print queue need Pro or above).
Kiri:Moto itself does - it has multi-extruder device settings, a purge tower and a separate support toolhead. The limitation is ours: the way SimplyPrint currently hands a plate to Kiri:Moto carries a single filament, so a multi-material plate cannot reach the engine. Rather than quietly dropping the extra materials, we refuse the plate and say so. For an AMS, a CFS or any other filament changer today, switch the engine picker to OrcaSlicer, BambuStudio, ElegooSlicer or CrealityPrint - same interface, same files, one click.
No. Neither option installs software on your computer. Cloud slicing puts the work on our servers, so a Chromebook, an iPad, an Android tablet or a ten-year-old laptop all work. Local slicing loads the engine runtime into the browser tab and runs on your own processor, so it wants a reasonably capable machine - on a light tablet, pick cloud.
Kiri:Moto is brand-agnostic: it slices for nearly any FDM printer. We associate it with Creality and SainSmart machines in our engine suggestions, and it is the one to pick for a belt printer whoever built it. As SimplyPrint is an FDM platform, resin, CNC and laser output are not supported even where an upstream engine can technically produce them.
Kiri:Moto is included with your SimplyPrint account at every plan level, alongside PrusaSlicer, OrcaSlicer, BambuStudio, ElegooSlicer, CrealityPrint & Cura. Cloud slicing draws on your monthly cloud-slice allowance - the plan table further up this page shows the exact number. Slicing locally does not touch that allowance: the work happens on your own machine, so there is nothing for us to meter.
Only if you want the printer half. Kiri:Moto already runs in a browser at grid.space, so getting at it from a tablet or a borrowed laptop is not something we add - it was never the problem. What SimplyPrint adds is everything after the G-code: the printers connected to your account, the queue, and being able to slice one machine with Kiri:Moto and the next with OrcaSlicer without changing tools. If you just want to slice something and download it, Stewart's own site is the right place and we would rather you used it.
Compute. A browser tab gets a slice of one machine and a hard memory ceiling, and a big or dense model can walk straight into it - a slice that crawls, or a tab that gives up with an out-of-memory error. Our slicing servers have neither limit, so the cloud option is the answer for the plates the browser cannot finish. That is also why the two are metered differently: local slicing is unlimited because it costs us nothing, and cloud slicing draws on your plan's monthly allowance because it runs on hardware we pay for.
Yes, with no limit and no plan gate. Slicing locally with Kiri:Moto runs on your own processor, so there is nothing for us to meter and nothing for us to charge for - we have not put a counter on it and do not intend to. Cloud slicing is the metered one, because that runs on our servers.
Stewart Allen does, essentially single-handedly, with community pull requests here and there. Kiri:Moto is not a commercial product from a large manufacturer - it is one person's long-running open-source project, and it is free. If it is useful to you, back it: Patreon, GitHub Sponsors or PayPal. SimplyPrint has donated to it in the past and sent pull requests to its GitHub, and the more of our slicing that runs on Kiri:Moto, the more we will put back into it.
It is, at github.com/GridSpace/grid-apps. We run the engine unmodified and comply with its license, and we publish our own slicer-building process openly at github.com/SimplyPrint/slicer-builds. Stewart Allen has helped us directly with the in-browser slicer, and we credit Grid.Space on our credits page.

Table of Contents