# Requirements for running non-rust wasm? **URL:** \ **Category:** Community Tutorials & Video\ **Created:** [June 14, 2026, 4:35pm UTC](https://forum.dfinity.org/t/requirements-for-running-non-rust-wasm/71681 "2026-06-14T16:35:18Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![graial](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/graial/32/39419_2.png) [@graial](https://forum.dfinity.org/u/graial)\ **Post date:** [June 16, 2026, 9:09am UTC](https://forum.dfinity.org/t/requirements-for-running-non-rust-wasm/71681/8 "2026-06-16T09:09:58Z")
Oh wow, I completely misunderstood you original comment: > [@skilesare](#): > > a 40B instruction limit I thought you meant 40bytes per assembly line/instruction. 40 billion instructions sounds non-trivial, but less daunting. Regarding wordpress, I guess this is the one your are talking about right? > [@WASP: WordPress Advanced Security Platform on the Internet Computer (alternate solution)](https://forum.dfinity.org/t/wasp-wordpress-advanced-security-platform-on-the-internet-computer-alternate-solution/63674): > > TL;DR: This a solution we came up with until we are possibly able to run Wordpress entirely on a canister. WASP uses ICP canisters as a security and caching layer in front of WordPress backends. If a server dies, your sites automatically restore to a standby TEE server from blockchain backups within minutes. What WASP Is (And What It Isn’t) WASP is not about running PHP inside a canister. Instead, it’s a hybrid architecture where ICP canisters act as an intelligent edge layer that caches conten… I see the fellow mentioning that they need 200B cycles for a page load. > Now ruby also likely has a runtime that needs to run in wasm that will load your ruby code and do things. It is very unlikely that this ruby vm stops every 2-8 seconds and cedes control back to the replica to record state I will take a look at the icp demo backends to better understand what you are talking about here and how the memory gets persisted from run to run. for example, does the IC runtime send a progression of kill messages that increase in severity as it approaches the DTS limit? It seems as though you are saying that IC canisters are pretty much limited to individual lambdas/functions, and you’d need to rig a bunch of them together to perform workflows, etc. > [@skilesare](#): > > so why not lean in? I mean, that’s pretty much what my initial inquiry is no? How far I lean in is TDB, a lot of this is new for me and just a lil hobby project. It’s much easier now on the ruby-side also, ruby-wasm shipped its first release in 2021 I think. I do think that IC is gonna need to define a target-triplet (or whatever you wanna call it). So that the appropriate build flags can evolve with the spec/standard. If IC’s objective is to become a runtime that wins widespread adoption at least. Cheers --- _[View the full topic](https://forum.dfinity.org/t/requirements-for-running-non-rust-wasm/71681)._