Medius AI

mediusai

Building a Global Production Ready Marketplace With Medusa JS

Headless commerce has been out there for a long while with Medusa being one of the best tool to offer modular components. Medusa’s composable architecture allows you to build a store with any framework or language of your choice hence providing a full customization ability. Medusa equally allows you to build a unique ecommerce experience by providing a set of tools and essential building blocks developers can add up to create a powerful ecommerce website. It offers out-of-the-box features like customer, product, shipping, tax and region management, and RMA Flow. In today’s tutorial, you will learn how to add a file service plugin in order to be able to add products to your Medusa store via the admin dashboard What is Medusa Medusa is an open-source set of tools that allow you to build amazing and reliable ecommerce websites. With more than , this headless commerce solution comes with a handful of commerce modules from basic to advanced and is freely available. Its also contributes to its success as there are step-by-step guidelines on how to add a module or plugins. Some popular plugins among others are payments, notifications, search and file service plugins. 17.8k stars and 1.3k forks on GitHub well-written documentation What is a File Service Plugin A file service plugin allows you to host files like images used in Medusa. You may face issues if you don’t use or set up a file service for your Medusa store properly. Medusa offers three different ways to manage file storage; S3, and . This tutorial solely focuses on S3 file storage to store images and files uploaded in Medusa. MinIo Spaces S3 or Simple Storage Service is an object storage used to store and retrieve any amount of data from anyway and at any time. We will use Amazon S3 for this demonstration. How to upload files into your Medusa store Amazon keeps data as objects within a bucket. An object consists of a file and optional data that describes it. To store a file, you need to upload it in a bucket(Buckets are the containers for objects), once uploaded, you can . set permissions on the object Now let’s get you to upload files in your Medusa projects quickly. Prerequisites . A Medusa project is basically divided into three components; a storefront, an admin dashboard and a A Medusa store Medusa Backend An AWS account If you have everything set up then follow the steps below to add a File Service Plugin to Your Medusa Store. Step 1: Create an S3 Bucket Login into your AWS account, search and select S3 In the next page, Click on Create bucket In the window that opens, provide the information necessary to create your bucket. General Configuration Provide a name to your bucket and leave the default region or choose another one per your requirements. Object Ownership For ownership, allow objects in the bucket to be owned by your account. In the Block Public Access settings, uncheck all public Access. Doing this will show a warning message check the box in the message as in the image. Block As for the Bucket versioning, tags, default encryption and advanced settings, leave the default settings or change them per your project requirements and click on . Create bucket Step 2: Manage Policies The next step consists of managing your created bucket policies. Head to the page of your bucket and open the Then scroll down to the bucket policy section, click on edit, add the code below and permission tab. Save. {
 "Version": "2012-10-17",
 "Id": "Policy1397632521960",
 "Statement": [
   {
     "Sid": "Stmt1397633323327",
     "Effect": "Allow",
     "Principal": {
       "AWS": "*"
     },
     "Action": "s3:GetObject",
     "Resource": "arn:aws:s3:::<YOUR_BUCKET_NAME>/*"
   }
 ]
} Replace with the name of your bucket. Here it is <YOUR_BUCKET_NAME> medusastorebucket Step 3: Attach a Policy In your account navigate to IAM and select Access Management->Policies in the left menu. If this is your first time choosing a policy, then you will see a Welcome to Manage Policies Page and select get started else choose Create policy. Then select the JSON tab and add the following code: {
  "Version": "2012-10-17",
  "Statement" : [
    {
      "Effect" : "Allow",
      "Action" : [
        "action-statement"
      ],
      "Resource" : [
        "resource-statement"
      ]
    },
    {
      "Effect" : "Allow",
      "Action" : [
        "action-statement"
      ],
      "Resource" : [
        "resource-statement"
      ]
    }
  ]
} Substitute the and per your requirement and click on action-statement resource-statement Next:tag Learn more about Policies and permissions Tags are optional so you can skip this step and click on the review button to review your policy. Next, provide a name and description for your policy then click on Create policy Now that you have created your policy, you need to attach it to a user group, navigate to and choose . Select the name of the group then open the Amazon console User Groups Permission tab Choose and then Add permission attach policies In the window that opens, select the policy you want to attach and click on add permission at the bottom of the page. Step 4: Get Your Access Key You need to obtain your access key in order to integrate the S3 Plugin into your project. You will need two elements; and . Access Key ID Secret Access Key To get your AWS Access Key ID and Secret Access Key, head to your on the left navigation, and choose Amazon console Users. Choose your and open the IAM user name Security credentials tab Scroll down to Access Keys and click on Create Access Key In the next window, you will be asked to choose where you want to use the access key. Check if you are working in a local dev environment. Local code By choosing local a warning message will appear asking you if you understand the recommendation. Check the box and click on the next button. Finally, add a tag description if you like to add one and click on Create access key In the next window, you will see your Access and Secret Access key. Kindly copy and paste it somewhere on your PC since you will use it in the next step or download the CSV file. Step 5: Install the S3 Plugin Now that you have set up your bucket and created your access keys, it’s time to install the S3 plugin. To do so head to your Medusa backend folder and install it with the following command: yarn add medusa-file-s3 Or npm install medusa-file-s3 Then open your file and add the following .env S3_URL=<YOUR_BUCKET_URL>
S3_BUCKET=<YOUR_BUCKET_NAME>
S3_REGION=<YOUR_BUCKET_REGION>
S3_ACCESS_KEY_ID=<YOUR_ACCESS_KEY_ID>
S3_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY> Where is the URL of your bucket. It is in the form . Where is the name of your bucket, the region. <YOUR_BUCKET_URL> https://<BUCKET_NAME>.s3.<REGION>.amazonaws.com <BUCKET_NAME> <REGION> is the name of the bucket created <YOUR_BUCKET_NAME> the region of your bucket <YOUR_BUCKET_REGION> <YOUR_ACCESS_KEY_ID> is your Access Key is your Secret Key <YOUR_SECRET_ACCESS_KEY> Finally in your add the following code: medusa-config.js const plugins = [
  // ...
  {
    resolve: `medusa-file-s3`,
    options: {
        s3_url: process.env.S3_URL,
        bucket: process.env.S3_BUCKET,
        region: process.env.S3_REGION,
        access_key_id: process.env.S3_ACCESS_KEY_ID,
        secret_access_key: process.env.S3_SECRET_ACCESS_KEY,
    },
  },
] Note that if you have many storage plugins configured, then the last plugin declared will be used. So if you want S3 to be used make sure it’s the last storage plugin added. Step 6: Testing the Plugin Now that you have successfully added your plugin. It’s time to test to make sure that everything is in the right place. You can use or the Medusa Admin to test. REST APIs Navigate to your admin and backend folders respectively and run the following command: // admin 
yarn run start // backend
yarn run start The default admin email and password are and respectively. Open your admin panel with admin@medusa-test.com supersecret http://localhost:7000/ In the menu click on then . Provide details for your product and publish it. Products Add Product Lastly, you need to add a configuration in your storefront that adds the S3 bucket domain name into the configured images’ domain names if you are using . If you don’t do it you will receive the following error . NextJS storefront next/image Un-configured Host So in your add the following: next.config.js const { withStoreConfig } = require("./store-config") // ...module.exports = withStoreConfig({
  // ...
  images: {
    domains: [
      // ...
      "<BUCKET_NAME>.s3.amazonaws.com",
    ],
  },
}) represents the name of your bucket. <BUCKET_NAME> Run your storefront with to check if the new products you added are there and proceed to the next phase of your project. yarn run dev Conclusion This marks the end of this tutorial, hopefully, you were able to add a file service plugin to your Medusa store. To get the best of the tool, consider adding payment services, search and notifications services.

Adding a File Service Plugin to Your Medusa Store: An Essential Guide

Agregar un complemento de servicio de archivos a su tienda Medusa: una guía esencial

Ajouter un plugin de service de fichiers à votre boutique Medusa : un guide essentiel

अपने मेडुसा स्टोर में एक फ़ाइल सेवा प्लगइन जोड़ना: एक आवश्यक मार्गदर्शिका

ファイル サービス プラグインを Medusa ストアに追加する: 基本ガイド

Adicionando um plug-in de serviço de arquivo à sua loja Medusa: um guia essencial

Thêm Plugin dịch vụ tệp vào Cửa hàng Medusa của bạn: Hướng dẫn cơ bản

将文件服务插件添加到您的 Medusa 商店：基本指南

Introduction With the growth of the internet and the evolution of technology, there is a need for businesses dealing in the e-commerce sector to remain competitive by keeping up with the latest trends in the area. Medusa is a popular open-source headless e-commerce solution developed recently, scalable, and flexible, making it one of the best choices for building an e-commerce website. It comes with two storefronts NextJs and Gatsby from which you can choose one, or use a different stack for your storefront since Medusa has a composable architecture allowing you to use different technologies for your front and backend; hence, giving you the possibility to fully customize your store and creating a store that will fit your needs. In this article, you will get started with Medusa by building your first headless store with a single command. Why Medusa? Medusa is an user and developer-friendly platform for building incredible webshops. open-source With over , its architecture allows you to build your online commerce shop with any framework of your choice, that is, developers have full control over their tech stack and the logic behind the commerce features. 17.8k stars on GitHub Besides that, it offers multi-regional support, advanced features for promotion and RMA flows, a user-friendly admin interface, and a community to support users. How to Build a Medusa Webshop You will learn how to build your first webshop with just a single Medusa command. However, make sure you have the following elements installed and working properly: version 16 or latest. To check your Node.js version, open your terminal or command line and run If you don’t have Node installed, then head to the , and follow the instructions to get it running on your OS. Node.js node -v. official website Git A package Manager( or ) Yarn Npm Medusa CLI Now, let’s get started. The first step will be to install the . You can’t use Medusa without installing its command line. Run the following command to get it set up: Medusa CLI yarn global add @medusajs/medusa-cli Or npm install @medusajs/medusa-cli -g Upon installing the CLI, check the version by running the following command in your terminal: medusa -v If you ever encounter errors installing the CLI, then visit this Medusa to get everything up. troubleshooting guide Creating Your Webshop With Create-Medusa-App Medusa is divided into three main parts: Backend — It’s the commerce engine Storefront — The actual webshop Admin Dashboard — An application to manage your store(add/remove products, collections, payment methods, manage customers…) Step 1: Install Your Webshop With Create-Medusa-App Open a terminal in your desired directory, and run the following command: npx create-medusa-app NB: When you install your project with this command, it comes with . Tailwind CSS Step 2: Specify the Project Name You need to specify the name of your webshop or leave the default value . Here we will name the store . my-medusa-store my-headless-store ? Where should you project be installed? . my-headless-store Step 3: Choose a Backend Starter Once you have named your store, the next step is to choose a . Here, we will be using Medusa starter medusa-starter-default ? Which Medusa starter would you like to install? …
❯ medusa-starter-default This Medusa starter contains admin plugins, which will allow you to later access the admin dashboard. All the resources for the backend will be installed in the backend directory. Step 4: Choose a Storefront Starter The next consists of choosing the Medusa starter for your storefront. Here, we will be using the NextJS starter: ? Which storefront starter would you like to install?
❯ Next.js Starter Your will be installed in the storefront directory. storefront Now, you need to wait until your project sets up completely before testing your store. Step 5: Test Your Store Upon installing all components of your project, you will see find three folders in your project directory. Admin Backend Storefront To start each component of your project, navigate to each component root and run the commands as follows: Your project is ready. The available commands are: // Medusa API
cd my-headless-store/backend
yarn start // Medusa Admin
cd my-headless-store/admin
yarn start // Storefront
cd my-headless/storefront
yarn dev To view your store and , open your favorite browser and type and in the address bar respectively. admin dashboard localhost:7000 localhoat:8000 Your store should look like the image below: And your dashboard: To access the dashboard, use as the email. admin@medusa-test.com as the password. supersecret Well, if you have reached this stage that means you have successfully set up a basic web shop with Medusa, however, if you run into any trouble, reach out on this website or reach out to the for further assistance. Medusa Discord channel Conclusion Hopefully, you have learned how to build a basic store with Medusa; now you need to customize your store and add plugins and services like: Payment methods with , , or . Klarna Paypal Stripe Notification services with , , or Twilio SMS. SendGrid Mailchimp Search functionality with Algolia or MeiliSearch. File upload Services with S3, Space, or MinIO. Shipping method. Gift cards. Just head to the full to get the necessary instructions to fulfill each task. Equally, feel free to sign up for our newsletter in order to get the latest e-commerce-related content. Medusa Documentation First published here

Building a Medusa WebShop With One Command

Since its inception, has held onto the mission of empowering future pop culture brands with an end-to-end supply chain of digital and phygital collectibles and providing global consumers access to new DTC experiences. Mighty Jaxx As they grew alongside the demand for their phygital products, venturing into the world of NFTs was a natural evolution for their collectibles by adding a new layer of verifiable ownership by certifying the authenticity of each toy and keeping a digital log of ownership. After the success of their first NFT which sold out shortly after its launch, Singapore-based future culture company has launched their latest exclusive drop featuring artist Jon-Paul Kaiser, the . Inked Stories: Eve Mighty Jaxx Inked Stories: Medusa This piece of art represents Greek tales of Medusa with a contentious appearance sculpted by Mighty Jaxx and tattoos designed by JPK. The drop will have a limited supply of 888 NFTs available for purchase from now until 21 October at 11am SGT. This limited edition NFT will exclusively grant holders the ability to purchase the physical figurine on 22 October 2022. Inked Stories: Medusa To ensure that the process of acquiring the digital collectible remains simple and seamless as they continue to expand into web3, Mighty Jaxx has also partnered with Paper, a web3 on-ramping infrastructure company that abstracts away the complexities of web3 so that buyers can make NFT purchases just as they would on any e-commerce site via a credit card. " is a web2 brand that is leveraging web3 technology to provide real-world utilities to our customers. While the physical collectible has always been our core business and that will not go away, the intention is to take what we have and amplify it both digitally and phygitally. Mighty Jaxx We hope to embrace technology innovations that combines the best of both physical and digital worlds and connect all our fandoms onto the MightyVerse,” said Darryl Tan, Head of Meta for . Mighty Jaxx is pioneering the path to enable collectors to have a verifiable record of their collectibles in both the digital and physical world. Mighty Jaxx Their previous product releases with extended digital experiences include , whereby users can unlock in-game loots with the physical collectible. Tiny Tina’s Wonderlands Looking ahead, the future culture company will be developing more real-life experiences, the MightyVerse, and digital collectibles and work towards a true hybrid phygital offering via their platform that will re-imagine the full-experiential journey for all fans and create value for them. As the digital and physical world continues to converge, proof of ownership will only become more important for highly sought-after collectibles like the as verified provenance will prove the authenticity of a collectible and greatly increase its value. Inked Stories: Medusa NFT owners will also have EXCLUSIVE access to the physical Medusa figurine. Sculpted by , you’ll be able to examine every story-inspired tattoo in real life! Stay tuned for updates on the pre-order launch and more exclusive releases. Mighty Jaxx To purchase Inked Stories: Medusa, visit while stocks last! https://mightymeta.world/medusa

Mighty Jaxx is Building Their MightyVerse With Their Latest NFT Drop Inked Stories: Medusa 

TL;DR Check out : Medusa The headless open-source Shopify alternative in Node.js Lowering the bar for when developers and merchants can build headless 5k stars since Sep and already in production at global eCommerce clients What is it? is the open-source alternative to Shopify. It is a commerce backend in Node.js covering E2E commerce features (e.g. order handling, admin system, product creation) but is built open-source and headless to maximize developer flexibility. Medusa The architecture is built for composability, giving you integrations to popular headless CMSs; shipping and payment providers; marketing, analytics and search solutions etc. Simultaneously, it comes with starters for both Next.js and Gatsby on the frontend. At last, it has natively built-in multi-regional support enabling you to localize currency, shipping, payment, and tax for each market you operate in. Headless Commerce for All Medusa aims to lower the bar for when developers and merchants can start building headless commerce applications. For years, the headless approach has been an enterprise exclusivity due to the large number of developer resources it requires to build a storefront and maintain backend infrastructure. Medusa lowers the bar by: Removing the need for a complex infrastructure through a clever plugin architecture. The core engine and all plugins run as part of the same Node.js server which is contrary to how other headless platforms need connectors and translation layers between the commerce engine and third-party services. The solution is optimized for the developer experience through strong tooling such as quick-starters, documentation, CLI, references, etc. to reduce the constraints put on the developer. The Story behind Medusa Medusa was originally built as a bespoke platform for almost three years ago. They wanted to switch away from WooCommerce to a more composable setup that enabled them to switch the tech stack as they grew and that could be easily scaled across markets. With solutions like Shopify, this type of customization would require a lot of "hacking" which their engine is not built for, and with no evident alternatives, the only viable option was to build it from scratch. TEKLA Fabrics The solution was later named Medusa and was fully open-sourced in August. The platform has since supported online selling all across the world from global brands to local D2C stores. The project managed to hit 5,000 GitHub stars before Christmas while counting a Discord community of +700 members. For more info check out our webpage - and feel free to reach out to the which is always ready to support new use cases and help you get started! here Medusa Community First published here

Looking for an Open Source Alternative to Shopify? Try Medusa

Artist Mieke Marple is committed to donating 25% of the proceeds from the Medusa Collection to fund alternative curriculums. , which was released today, isn’t Mieke Marple’s first NFT drop, but it is a drop with a higher cause -- to put aside what we know of the world’s most famous gorgon and re-examine the story of the woman behind the snakes. It is also an effort to raise money for TeachRock, an organization dedicated to providing alternative curriculums for use by educators that includes music and pop culture references meant to be more engaging and relatable for children. The Medusa Collection TeachRock was founded by luminaries of music and show business including Stevie “Little Steven” Van Zandt, Bono, Jackson Browne, Martin Scorsese, and Bruce Springsteen. Marple is carrying over the same “rock n’ roll” energy of challenging assumptions in this drop. By making the donation through Endaoment, the first on-chain 501(c)(3) nonprofit public charity, they are able to make the donation tax-exempt -- though I do not believe that’s the case for purchasers of the NFTs. Endaoment states that it has already facilitated $10,797,101 in donations at the time of writing. on its website TeachRock is a free and open-source curriculum extension endorsed by the National Councils for Social Studies, Geographic Education, and Music Education, and is an official component of the New Jersey School Boards Association’s STEAM education program. It provides more than 300 educational resources and works directly to over 100 schools across five states. "TeachRock works tirelessly to keep the arts in the DNA of the public school system,” said TeachRock founder Stevie Van Zandt. “Now we're using the arts to raise the money to pay for that work too. This NFT project encourages us to rethink the true story of a myth we all grew up with and funds a new curriculum that will share that story freely with teachers and students worldwide." The Medusa Collection consists of 2,500 generative art NFTs based on Marple’s paintings of canonical Italian sculptures of Medusa, circa 1545 to 1805. The collection was inspired by , which tells the story of Medusa having been raped by the god Poseidon and then turned into a monster by his wife, Athena, as punishment for being assaulted. The myth is often taught in schools without really examining who, by the standards of modern society, is really the monster in the story. Ovid’s Metamorphoses Maple took the time to give us some insights concerning her work as an artist, the message behind the art, and the experience of doing the NFT drop. Mieke Marple When did the project start? “I started working on the Medusa NFT Collection at the end of August 2021. However, I started making IRL Medusa paintings—based on canonical Italian sculptures of Medusa—in the summer of 2019. These paintings were exhibited in my “Bad Feminist” solo show at Ever Gold Projects SF in November 2019,” Marple said. Tell me about your journey -- how did you get involved with this TeachRock? When did you start working in NFTs? “I made my first NFTs in February 2019. They were 1:1 digital twins of my IRL tarot paintings. They sold right away to an amazing collector, Jehan Chu, who is a partner at Kenetic Capital and a crypto advisor to Christie’s. Jehan invited me to participate in an eight-artist benefit NFT auction with Beeple, Refik Anadol, and other amazing artists for Open Earth this past March, just two weeks after Beeple’s $69M sale at Christie’s. So I’ve had a very charmed NFT journey, you could say. I met Bill Carbone, the director at TeachRock, at a panel about Social Impact Organizations and NFTs. I told him about my 2019 Medusa paintings, which I made after learning that Medusa was actually a rape victim: she was raped by the god Poseidon and turned into a monster by his wife, the God Athena. Bill told me that updating problematic school curricula (a.k.a. restorative history) and using the arts to increase engagement was at the heart of what TeachRock did. The Medusa Collection, which aims to reframe the Medusa myth on a global scale, was born from this conversation,” Marple said. What have NFTs meant for you as an artist? “Before I was a traditional artist, I was a traditional art dealer. I was co-owner of a successful contemporary art gallery called Night Gallery in LA. In other words, I came of age in the hoity-toity world of high-end art. For me, getting into NFTs means shattering all that the traditional art world indoctrinated within me. It means connecting directly with the buyers of my work, who are not just the 1% of the 1%, but are a diverse range of people from all over the world,” Marple said. What can NFTs allow you to do that you couldn't do before? “Scale. Scale. Scale. I could never make 2500 unique Medusa paintings IRL—and then somehow coordinate the shipping of those. Can you imagine? It would require a team of 100 people! Which is something only a mega-artist like Jeff Koon has. NFTs allow me to do something really ambitious with a relatively small heart-driven team. I can engage way more people, in way more places, than I ever could via an IRL gallery exhibition,” Marple said. What is the scarcity structure of this project? “There are ten different variables for each Medusa head, including head type, skin color, background, etc—some variable options appear 40% of the time, others 0.5% of the time. Fourteen of the 2500 are also hand-designed by me (i.e. not created by the algorithm). Four of those 14 have a very special Medusa head (based on a sculpture of Medusa from 1850 by an American woman) that does not appear anywhere else in the collection. There are also inverted Medusas and Medusas coupled with rare symbolic objects—roses, apples, pomegranates, etc.—inspired by Dutch still lifes,” Marple said. Are there any utility tokens/other incentives/tokenomics? “Yes! I am going to release a follow-up 2500 NFT generative project (that may or may not involve Pegasus) that all Medusa holders will get for free. Basically, you will have to own a Medusa to get my next generative NFT. I’m also doing giveaways of my IRL Medusa prints and paintings to random holders as we reach certain sales milestones. TeachRock is also giving away a signed Stevie Van Zandt guitar to a random holder when we sell out. I’m also setting up a Shopify for people to buy Medusa NFTs via credit card. They will still need to set up a Metamask wallet. But I will do the minting for them and then transfer the Medusa NFT to their wallet. This is to help reduce some of the barriers to entry that discourage many women and marginalized groups from participating in NFTs,” Marple said. What is the message to your community? “I want to inspire in my community the same thing that they have inspired in me. Honestly, I cry when I think about it sometimes. But it is 100% my Medusa team and community that has helped me get through a lot of self-doubt and fear. They inspire me to put myself out there, be generous, take risks, and talk about difficult subjects. They help me believe in myself and I want to do the same for them. I want the Medusa Collection to help others harness their creative superpowers as well as the power of their own hearts,” Marple said. What are your next steps after the drop? “Keep doing fun, heartfelt events and contests with the community and start making the work for my next generative project! I’m also working on a body of IRL paintings for an exhibition with Ever Gold [Projects] in March 2022 on the David Zwirner backed Platform,” Marple said. Conclusion We need more drops like this in the NFT space -- it has vision and substance. As art, it has a message and a sense of intent that makes the work riveting, and it has a purpose, to raise money for an established non-profit. If other art NFT projects follow the creative model of this project, we can look forward to more interesting and engaging projects entering the space. The Medusa project already has an ongoing life planned after launch -- TeachRock has committed to supporting the research and development of a Medusa Reconsidered unit within their World Mythology curriculum. Cover art: Detail from Medusa from the Medusa Collection

Medusa Collection NFTs set its Gaze on Raising Money for TeachRock

HackerNoon Reporter: Please tell us briefly about your  background. My adventure in healthcare started in 2011 when, with a friend of mine, I founded a company that is now called SkinVision, a skin cancer screening app. I was responsible for product and research so that is where I’ve gathered most of my experience in healthcare and got a first hand view of the challenges. What's your startup called? And in a sentence or two, what does it do? Medicai is the name of the startup and it is a web based medical imaging platform that changes the way doctors and patients coordinate care, especially for chronic or rare conditions that require handling of complex medical data - i.e. imaging, digital pathology etc What is the origin story? In 2018 I wanted to do something else after I left my first company. I gathered a team made up of people I worked with in the past and we started exploring. We have experience in computer vision and AI so medical imaging made sense but when we started talking to stakeholders we realised we were surrounded by CDs (which don’t really mix with AI). We started looking into why this is still happening and realised we could make a big difference by changing the way doctors and patients interact. The question actually is: how would interactions between doctors and patients change if had an online tool that allows instant collaboration on those “data sets” - i.e. what if, as a patient, I could view/edit my MRI scan together with my doctor directly online? What do you love about your team, and why are you the ones to solve this problem? I feel we have reached a point where everyone is aligned in doing what is best for the company and we can now focus on that. I believe culture is crucial and we managed to create an open and inclusive environment that can help us build to last. If you weren’t building your startup, what would you be doing? Building another startup? At the moment, how do you measure success? What are your core metrics? We are still very much in the product building phase so we measure engagement and usage. We want a great product so we focus on what our users want and need. Any KPI that can help us better understand what our users want/need is important so DAU/MAU, time spent on avg. -  that type of thing What’s most exciting about your traction to date? We see a lot of doctors using the platform every day for multiple hours. Doctors are notoriously difficult to convert and that’s why we’re pretty happy about it. On top, we have a real chance of changing things in a very important field to many people What technologies are you currently most excited about, and most worried about? And why? We focus on AI and we strongly believe it will change a lot of things in healthcare but also that we are not there yet. A few things need to change so that AI can be adopted and one of them is infrastructure. What drew you to get published on HackerNoon? What do you like most about our platform? The community of like-minded people and the quality of the content. What advice would you give to the 21-year-old version of yourself? Dig deeper. What is something surprising you've learned this year that your contemporaries would benefit from knowing? I don’t know. I guess I’m not sure others would be surprised by it:) Vote for Medicai for Startup of the Year, Bucharest

On Rebuilding the Future Of Medical Imaging: Mircea Popa, Medicai Co-Founder

Microarchitectural Security of AWS Firecracker VMM: Analysis of Microarchitectural Attack & Defenses

AWS ফায়ারক্র্যাকার VMM এর মাইক্রোআর্কিটেকচারাল সিকিউরিটি: মাইক্রোআর্কিটেকচারাল অ্যাটাক এবং ডিফেন্সের বিশ্লেষণ

Mikroarchitektonische Sicherheit von AWS Firecracker VMM: Analyse von mikroarchitektonischen Angriffen und Abwehrmaßnahmen

Seguridad microarquitectónica de AWS Firecracker VMM: análisis de ataques y defensas microarquitectónicas

Sécurité microarchitecturale d'AWS Firecracker VMM : analyse des attaques et des défenses microarchitecturales

AWS फायरक्रैकर VMM की माइक्रोआर्किटेक्चरल सुरक्षा: माइक्रोआर्किटेक्चरल हमले और बचाव का विश्लेषण

AWS Firecracker VMM のマイクロアーキテクチャセキュリティ: マイクロアーキテクチャ攻撃と防御の分析

AWS Firecracker VMM의 마이크로아키텍처 보안: 마이크로아키텍처 공격 및 방어 분석

Segurança microarquitetônica do AWS Firecracker VMM: análise de ataques e defesas microarquitetônicas

Микроархитектурная безопасность AWS Firecracker VMM: анализ микроархитектурных атак и защиты

AWS Firecracker VMM'nin Mikro Mimari Güvenliği: Mikro Mimari Saldırı ve Savunmaların Analizi

Bảo mật vi kiến trúc của AWS Firecracker VMM: Phân tích tấn công và phòng thủ vi kiến trúc

AWS Firecracker VMM 微架构安全：微架构攻击与防御分析

Microarchitectural Security of AWS Firecracker VMM: Background

AWS ফায়ারক্র্যাকার VMM এর মাইক্রোআর্কিটেকচারাল নিরাপত্তা: পটভূমি

Mikroarchitektonische Sicherheit von AWS Firecracker VMM: Hintergrund

Seguridad microarquitectónica de AWS Firecracker VMM: antecedentes

Sécurité microarchitecturale d'AWS Firecracker VMM : contexte

AWS फायरक्रैकर VMM की माइक्रोआर्किटेक्चरल सुरक्षा: पृष्ठभूमि

AWS Firecracker VMM のマイクロアーキテクチャセキュリティ: 背景

AWS Firecracker VMM의 마이크로아키텍처 보안: 배경

Segurança microarquitetônica do AWS Firecracker VMM: histórico

Микроархитектурная безопасность AWS Firecracker VMM: предыстория

AWS Firecracker VMM'nin Mikro Mimari Güvenliği: Arka Plan

Bảo mật vi kiến trúc của AWS Firecracker VMM: Bối cảnh

AWS Firecracker VMM 的微架构安全性：背景

Microarchitectural Security of AWS Firecracker VMM: Conclusion, Acknowledgments, and References

AWS ফায়ারক্র্যাকার VMM এর মাইক্রোআর্কিটেকচারাল নিরাপত্তা: উপসংহার, স্বীকৃতি এবং রেফারেন্স

Mikroarchitektonische Sicherheit von AWS Firecracker VMM: Fazit, Danksagungen und Referenzen

Seguridad microarquitectónica de AWS Firecracker VMM: conclusión, reconocimientos y referencias

Sécurité microarchitecturale d'AWS Firecracker VMM : conclusion, remerciements et références

AWS फायरक्रैकर VMM की माइक्रोआर्किटेक्चरल सुरक्षा: निष्कर्ष, आभार और संदर्भ

AWS Firecracker VMM のマイクロアーキテクチャセキュリティ: 結論、謝辞、参考文献

AWS Firecracker VMM의 마이크로아키텍처 보안: 결론, 승인 및 참조

Segurança microarquitetônica do AWS Firecracker VMM: conclusão, agradecimentos e referências

Микроархитектурная безопасность AWS Firecracker VMM: заключение, благодарности и ссылки

AWS Firecracker VMM'nin Mikro Mimari Güvenliği: Sonuç, Teşekkür ve Referanslar

Bảo mật vi kiến trúc của AWS Firecracker VMM: Kết luận, Lời cảm ơn và Tài liệu tham khảo

AWS Firecracker VMM 的微架构安全性：结论、致谢和参考文献

Stories, News & Mentions about MEDIUSAI

Mediusai’s Stories on HackerNoon