# How it Works

From *Vibe Code*\
to Production —
---------------

<mark style="color:$primary;">The Problem</mark>

Vibe coding gets you to a working app in minutes. But working isn't production. Vibe-generated code ships without real auth, no Dockerfile, no container config, no CI/CD, no health checks, no audit trail.

<mark style="color:$primary;">What Vibe-Shift does</mark>

VIBEshift is Opsera's autonomous DevOps agent. It takes your vibe-coded app directly from GitHub, detects your stack, generates a Dockerfile, provisions AWS EKS infrastructure, and deploys your app to production — no CI/CD knowledge, no YAML, no Terraform required.

<figure><img src="/files/EAVKhTHZDzaHvxgxaW3d" alt=""><figcaption></figcaption></figure>

<mark style="color:$primary;">The result</mark>

A production-grade application running on AWS EKS, with production-ready OAuth, health verification, and a full audit trail.

## 6 Autonomous Steps.

**No human required.**

<figure><img src="/files/slq2Im3K6n0AmuQxZCYs" alt=""><figcaption></figcaption></figure>

Vibe-Shift runs a full production pipeline against your repo — automatically, in sequence, with self-healing built in at every stage.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><mark style="color:$primary;">Step 01</mark></p><h4>Stack </h4><h4>Auto-Detection</h4><p>Reads your repo and identifies Node.js, Python, React, or Next.js — no configuration file needed. Vibe-Shift  figures out what you built so you don't have to tell it.</p></td></tr><tr><td><p><mark style="color:$primary;">Step 02</mark></p><h4>OAuth </h4><h4>Migration</h4><p>Detects existing OAuth flows and upgrades them to Express + Passport.js for production-grade security — automatically, with no manual code changes required from you.</p></td></tr><tr><td><p><mark style="color:$primary;">Step 03</mark></p><h4>Dockerfile </h4><h4>Generation</h4><p>Creates a production-optimised Dockerfile from your detected stack. This is the only file committed to your repo — clean and minimal. Nothing else touched.</p></td></tr><tr><td><p><mark style="color:$primary;">Step 04</mark></p><h4>Self-Healing Deployments</h4><p>Monitors rollout health in real time and automatically retries failed steps — up to 5 times before alerting you. Most issues resolve without you ever knowing they happened.</p></td></tr><tr><td><p><mark style="color:$primary;">Step 05</mark></p><h4>Health </h4><h4>Verification</h4><p>Validates that pods are running and service endpoints are responding before marking the deployment complete. Your app is confirmed live — not just deployed.</p></td></tr></tbody></table>

## **GitOps, Built In.**

Auto-deploy is on by default. The moment you push to main, Vibe-Shift  triggers the full 6-step pipeline — no commands, no manual steps. Your git push is your deployment trigger.&#x20;

## **Deploy From Your IDE.**

Vibe-Shift integrates natively with Claude Code, Cursor or VS Code via MCP. Type one command in your chat window and the agent handles the rest — end to end, autonomously.

That's it. Vibe-Shift does the rest.

{% stepper %}
{% step %}

### **One command deploy**

&#x20;The full pipeline runs from a single chat message in your IDE.
{% endstep %}

{% step %}

### **Deterministic execution**

Server-orchestrated, reproducible results, every time.
{% endstep %}

{% step %}

### **MCP-native**&#x20;

Code connects via HTTPS + OAuth Bearer token. SKU-filtered tool access per plan.&#x20;
{% endstep %}

{% step %}

### **Full observability**&#x20;

Every tool call, auth event, and deployment step is logged. Complete audit trail, always.
{% endstep %}
{% endstepper %}

### What Vibe Platforms Ship vs What Vibe-Shift Adds

|                                       | Vibe Platform | Vibe-Shift               |
| ------------------------------------- | ------------- | ------------------------ |
| Working code                          | ✅             | ✅                        |
| Production auth (OAuth / Passport.js) | ❌             | ✅                        |
| Dockerfile                            | ❌             | ✅ Auto-generated         |
| CI/CD pipeline                        | ❌             | ✅ GitOps, zero config    |
| Cloud infrastructure                  | ❌             | ✅ AWS EKS, fully managed |
| Health verification                   | ❌             | ✅ Pod + endpoint checks  |
| Failure recovery                      | ❌             | ✅ 5× auto-retry          |
| Audit trail                           | ❌             | ✅ Full PostgreSQL log    |

{% hint style="info" %}

* **Supported stacks:** Node.js, Python, React, Next.js&#x20;
* **Supported git providers:** GitHub, GitLab, Bitbucket **Supported clouds:** AWS EKS (Azure and GCP available via pipeline environment config) **Powered by:** Claude AI (Sonnet + Opus), MCP Protocol
  {% endhint %}

### Enterprise-grade infra.

**Fully managed. No customer VPC.**

Vibe-Shift provisions and manages all of the following on your behalf — you get production infrastructure without managing any of it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.agents.opsera.ai/vibe-shift/how-it-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.