Hey everyone,
I’m working on a small blog project called Remnants and I’ve hit a block — I don’t have cycles to deploy it on mainnet. Still in the learning/experimenting phase, so I was wondering if anyone could spare some cycles to help me get it live.
My account ID:
b77c27b7b81b0ee668d449f4e133ed2b9483fda82c6abd95048ea619d10844b9
Would really appreciate the support! 
Mathew Tas-007
Can you share some code ?
Sure happy to share. Do you want the full repo or just specific files (e.g. about.html, contact.html, deploy steps)?
Hi @MathewTas-007,
you can use https://icp.ninja which will enable you to host your project temporarily on IC mainnet. There is also the option to take full control over the project via the CycleOps integration.
I hope this helps.
Marco
Hi Marco,
Thanks a lot for sharing this! I checked out icp ninja, and it seems like a great way to quickly deploy my project to the IC mainnet.
Since I’m actively building and plan to keep adding features, I’d love your advice on the best practice here. Would you recommend sticking with icp Ninja for rapid iterations, or setting up CycleOps early for more control and smoother updates?
I appreciate any guidance you can share.
Best regards,
Mathew
As long as you do not need to make sure that backend data persists and that the canister ids of your project will always be the same, you can continue using ICP Ninja until you are ready for the go-live. You can redeploy anytime 
The updates can be smooth in both ways, but if you take control (e.g. via CycleOps), you need to pay for the cycles yourself (unless ICP Ninja provides you a free deployment, which may also happen 
).
Hi Marco,Thanks for clarifying! That makes sense — so as long as I’m okay with temporary canister IDs and non-persistent backend data, I can use ICP Ninja for smooth updates until I’m ready for a full go-live. Good to know about CycleOps and cycles — I’ll keep that in mind when it’s time for more control. Really appreciate the tips! 
Best,Mathew