# rawcode.ing

> rawcode.ing is a one-person software service that rescues AI-generated ("vibe-coded")
> applications: reading the codebase by hand, fixing what is broken or insecure, and
> deploying it to a real, maintained VPS. Run by an independent developer who writes code
> by hand and reads every line before it ships. Contact: hello@rawcode.ing

**Site:** https://rawcode.ing/ · **Contact:** hello@rawcode.ing · **Language:** English · **Availability:** remote, worldwide

## What "raw code" means

Raw code is code a human wrote, read, and can explain: the data model, the auth flow, the
failure modes, and the deploy path — out loud, with the laptop shut. AI is used as a tool
for boilerplate and lookups, not as an autopilot. The opposite is "vibe coding": prompting
an app into existence and accepting the output without reading it.

## The service

Aimed at people who prompted an app into existence and then hit reality — it won't build,
won't deploy, won't stay up, or was never safe to put in front of users.

- **Code audit.** The whole repo is read top to bottom before a line is changed. You get a
  straight answer about what is worth keeping and what should be thrown away.
- **Remediation.** API keys moved out of the client bundle. Input validated. Unused
  dependencies removed. Build made green. Tests written around anything touching money or
  user data.
- **Deployment and hosting.** Deployed to a managed VPS: nginx, systemd, a database that
  persists, TLS, a domain, and backups that leave the box. No cold starts, nothing that
  sleeps after 15 minutes of quiet. Deploying to your own cloud account is also supported.
- **Operations.** One-command or git-push deploys, documented so you can run them yourself.
  Alerts route to the developer's phone first, so you hear about an outage from him and not
  from a customer.
- **Handover.** You keep the repository, domain, DNS, accounts, and server configuration,
  plus a README and a deploy script. Help moving elsewhere later is included.

## How engagement works

Email hello@rawcode.ing describing the stack, what it does instead of working, and how long
it has been that way. You get a reply within one business day from a human, with a plan and
a real number — or a straight answer that it is past saving. There is no discovery call, no
sales deck, and no fixed price list; cost depends on the size of the problem.

## What is explicitly not offered

Pasting your repository into a chat window, accepting whatever comes back, and invoicing for
it. Any code handed over has been read line by line.

## Position on AI-assisted development

Vibe coding is genuinely good for prototypes, weekend projects, throwaway demos, and
learning. It becomes a liability once something holds money, user data, or an uptime
promise. The dividing line is ownership, not tooling: if you cannot explain how the system
works without opening a chat window, you did not build it — you were in the room while it
got built.

## Full content

- [Complete site text, services and FAQ](https://rawcode.ing/llms-full.txt): the full page
  content as plain markdown, including the nine symptoms of advanced vibe coding, the
  vibe-vs-raw comparison, the manifesto, and every FAQ answer.
- [Homepage](https://rawcode.ing/): the same content as HTML.