<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: vyomicloud</title>
    <description>The latest articles on DEV Community by vyomicloud (@vyomiadmin).</description>
    <link>https://dev.to/vyomiadmin</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3995488%2F7cf742e3-3003-4082-8268-f4e4e6b69156.png</url>
      <title>DEV Community: vyomicloud</title>
      <link>https://dev.to/vyomiadmin</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vyomiadmin"/>
    <language>en</language>
    <item>
      <title>Testing a multi-cloud app locally: LocalStack, Moto, Azurite… or one tool for all three?</title>
      <dc:creator>vyomicloud</dc:creator>
      <pubDate>Sun, 21 Jun 2026 15:54:05 +0000</pubDate>
      <link>https://dev.to/vyomiadmin/testing-a-multi-cloud-app-locally-localstack-moto-azurite-or-one-tool-for-all-three-2dd7</link>
      <guid>https://dev.to/vyomiadmin/testing-a-multi-cloud-app-locally-localstack-moto-azurite-or-one-tool-for-all-three-2dd7</guid>
      <description>&lt;p&gt;If your app only talks to AWS, &lt;strong&gt;LocalStack&lt;/strong&gt; is fantastic. But the moment a service reaches into GCP or Azure, local development fragments: you bolt on &lt;strong&gt;Moto&lt;/strong&gt; for extra AWS bits, &lt;strong&gt;Azurite&lt;/strong&gt; for Azure Blob, and the &lt;strong&gt;gcloud emulators&lt;/strong&gt; for Pub/Sub and Firestore. Three+ tools, three configs, no shared state, no shared console.&lt;/p&gt;

&lt;p&gt;This post compares the options for testing a &lt;em&gt;multi-cloud&lt;/em&gt; app locally, and introduces &lt;strong&gt;Vyomi&lt;/strong&gt; — what we call a &lt;strong&gt;multi-cloud digital twin runtime&lt;/strong&gt;: instead of mocking one cloud, it runs a faithful, &lt;em&gt;live&lt;/em&gt; replica of AWS, GCP, &lt;strong&gt;and&lt;/strong&gt; Azure in one appliance, on real backends. (If "simulator" is the word you searched for, that's the neighbourhood: the difference is the "real backends" part below.)&lt;/p&gt;

&lt;h3&gt;
  
  
  The landscape
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;th&gt;Clouds&lt;/th&gt;
&lt;th&gt;Backing&lt;/th&gt;
&lt;th&gt;Multi-cloud?&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;LocalStack&lt;/td&gt;
&lt;td&gt;AWS&lt;/td&gt;
&lt;td&gt;mocks + some real&lt;/td&gt;
&lt;td&gt;No (AWS only)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Moto&lt;/td&gt;
&lt;td&gt;AWS&lt;/td&gt;
&lt;td&gt;in-process mocks&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Azurite&lt;/td&gt;
&lt;td&gt;Azure Blob/Queue/Table&lt;/td&gt;
&lt;td&gt;real emulator&lt;/td&gt;
&lt;td&gt;No (single service)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GCP emulators&lt;/td&gt;
&lt;td&gt;GCP (Pub/Sub, Firestore, …)&lt;/td&gt;
&lt;td&gt;official emulators&lt;/td&gt;
&lt;td&gt;No (piecemeal)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Vyomi&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;AWS + GCP + Azure&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;real backends (digital twin)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Yes — one appliance&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Why a digital twin, not a mock?
&lt;/h3&gt;

&lt;p&gt;Instead of in-process mocks, Vyomi runs actual engines behind the cloud APIs: Postgres and MySQL for managed SQL, MinIO for S3, DynamoDB-local, Vault for KMS/secrets, NATS for eventing, Azurite for Azure Blob, fake-gcs-server for GCS, and the official Firestore / Pub-Sub emulators. Closer-to-prod behaviour, and state that persists.&lt;/p&gt;

&lt;h3&gt;
  
  
  The only change to your code: the endpoint URL
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="c1"&gt;# AWS (boto3)
&lt;/span&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;boto3&lt;/span&gt;
&lt;span class="n"&gt;s3&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;boto3&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;client&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;s3&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;endpoint_url&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;http://localhost:9000&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="c1"&gt;# GCP (google-cloud-storage) — point at the local endpoint
# Azure (azure-storage-blob) — same idea, one connection string
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;aws&lt;/code&gt;, &lt;code&gt;gcloud&lt;/code&gt;, &lt;code&gt;gsutil&lt;/code&gt;, &lt;code&gt;az&lt;/code&gt;, and &lt;code&gt;terraform&lt;/code&gt; work the same way.&lt;/p&gt;

&lt;h3&gt;
  
  
  When you're done: export to Terraform
&lt;/h3&gt;

&lt;p&gt;Vyomi exports your simulated stack to Terraform HCL, so the same resources you built locally &lt;code&gt;terraform apply&lt;/code&gt; to a real AWS/GCP/Azure account — local-to-prod without a rewrite.&lt;/p&gt;

&lt;h3&gt;
  
  
  Try it
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew &lt;span class="nb"&gt;install &lt;/span&gt;vyomi-cloud/tap/vyomi &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; vyomi up
&lt;span class="c"&gt;# or: docker run -d -p 9000:9000 -p 9443:9443 vyomi/appliance:latest&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Runs offline, free tier, source-available. &lt;br&gt;
Full feature-by-feature comparison: &lt;strong&gt;&lt;a href="https://vyomi.cloud/compare/localstack" rel="noopener noreferrer"&gt;https://vyomi.cloud/compare/localstack&lt;/a&gt;&lt;/strong&gt;. &lt;br&gt;
Source: &lt;a href="https://github.com/vyomi-cloud/appliance" rel="noopener noreferrer"&gt;https://github.com/vyomi-cloud/appliance&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this article is from the Vyomi team. Feedback and "you got LocalStack wrong here" corrections welcome.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>localstack</category>
      <category>aws</category>
      <category>devops</category>
      <category>cloud</category>
    </item>
  </channel>
</rss>
