# Remocal.dev

This microsite exists to explain this concept in more detail, go into some of the reasons why this matters & how teams can adopt it to ship faster, debug smarter & ultimately build with confience :muscle:

### Why remocal?

Traditional development workflows often force a choice:

* **Local-first:** Fast iterations, but not representative of the production environment
* **Remote-first:** Accurate, matches production, but slow & painful to iterate

Remocal development aims to bridge that gap by combining the best of both worlds:

| Local                        | Remote                          |
| ---------------------------- | ------------------------------- |
| Fast editing & great tooling | Production-grade environments   |
| Instant iteration            | Real APIs, real infrastructure  |
| Dev-experience is optimised  | Close-to-production deployments |

With remocal development, your code lives on your machine, but your app runs where it's meant to - in the cloud, in containers, on edge networks, or wherever else your users are.

### What you can find here

This microsite aims to be a guide to understanding, adopting & mastering remocal workflows.

{% hint style="warning" %}
This site is still under construction - please bear with us!
{% endhint %}

It covers:

* **What is remocal?** - A deeper dive into the pattern & philosophy
* **Why do remocal?** - Problems this aims to solve & trade-offs to be aware of
* **How to remocal** - Practical implementation patterns & workflows
* **Who is doing remocal?** - Real world examples & case-studies from others

When you're ready, let's get started!