# A demo instance on Azure using the K8S recipes

**URL:** <https://aiida.discourse.group/t/a-demo-instance-on-azure-using-the-k8s-recipes/64>\
**Category:** Ideas\
**Tags:** aiidalab\
**Created:** [August 3, 2023, 9:14am UTC](https://aiida.discourse.group/t/a-demo-instance-on-azure-using-the-k8s-recipes/64 "2023-08-03T09:14:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jusong.yu](https://yyz2.discourse-cdn.com/free1/user_avatar/aiida.discourse.group/jusong.yu/32/3_2.png) [@jusong.yu](https://aiida.discourse.group/u/jusong.yu)\
**Post date:** [August 3, 2023, 9:14am UTC](https://aiida.discourse.group/t/a-demo-instance-on-azure-using-the-k8s-recipes/64/1 "2023-08-03T09:14:00Z")

</div>

There are only two public deployment of AiiDAlab at the moment, one on Materials Cloud for MARVEL partners and one on DigitalOcean for EU-MarketPlace project which will soon terminated (end Sept).

We had a credential on Azure for the deployment of AiiDAlab, and we want to use it to have a Demo server that doesn’t have too many restrictions for new users to login. New users should be very easy to get a taste of how AiiDAlab (especially QeApp) works in minutes. Some consideration are list below:

Have a demo instance (where we delete everything after say 12 hours, and this is clearly written) on Azure using the K8S recipes

- Check costs
- Ensure there is a clear hard limit on costs
- link AAI to something where there is no risk of people mining bitcoins (SwitchAAI?)
- Have everything needed for a demo already there, no need for the user to go and install (use a custom image to reduce startup times?) See `aiidalab/qe:edge` image.