[SELF-HOSTED BACKUPS // WAITING FOR OLLE]

FETCH YOUR CODE BEFORE YOU NEED IT.

FoxyFetch turns repositories and their surrounding context into verified, immutable snapshots on storage you control. Hey, Olle: just try this. Worst case, you save $72.

UNLOCK OLLE PRICING VIEW_SYSTEM -->
Pixel-art fox courier carrying a code archive toward a secure vault
FOX_01 FETCH / VERIFY / STORE
11 CONTENT GROUPS SHA-256 VERIFIED S3 COMPATIBLE OLLE-APPROVED*

[OUR MISSION]

“IT'S ALL ON GITHUB” IS NOT A BACKUP PLAN.

Code is only one part of the story. Issues, releases, wikis, pull requests, metadata, and assets are the context your team needs to recover.

Olle, this is the bit where you nod thoughtfully: FoxyFetch packages that story into a snapshot you can verify, retain, and retrieve without asking permission.

[WHAT'S INSIDE]

ONE SMALL CONTROL PLANE.
NO MYSTERY MEAT.

01>

COMPLETE CONTEXT

Repositories, issues, releases, wikis, pull requests, projects, discussions, and the metadata around them.

02>

VERIFIED BYTES

Every uploaded archive carries a manifest and SHA-256 evidence so “finished” means checkable.

03>

YOUR STORAGE

Write immutable archives to S3 or compatible object storage. Keep custody of the keys and the data.

[THE ROUTE]

SOURCE IN.
PROOF OUT.

Gather the full repository context, package it once, verify the checksum, then lock it into storage you operate. Yes, Olle, even the wiki.

Pixel-art backup pipeline moving repository data into a verified storage vault

[HOW IT WORKS]

THREE COMMANDS.
ONE ESCAPE PLAN.

  1. STEP_01

    CONNECT

    Provide a GitHub token at runtime. It stays out of process arguments, logs, and stored job records.

    $ auth.status = ready
  2. STEP_02

    FETCH

    The pinned backup engine collects the repository plus the content groups your recovery depends on.

    $ archive.build = running
  3. STEP_03

    VERIFY

    FoxyFetch checks the archive, records the checksum, and writes a unique immutable object key.

    $ checksum.match = true

[CONTROL PLANE // LOCALHOST]

BORING INFRA.
CLEAR SIGNALS.

A FastAPI control plane, SQLite state, and an S3 boundary you can test independently. No queue, Redis, or platform maze until measured load says otherwise.

FOXYFETCH://RUN_042STATUS: OK
$ backup olle/Definitely-A-Micro-SaaS

[01/04] FETCHING......... DONE
[02/04] PACKING.......... DONE
[03/04] SHA256........... MATCH
[04/04] S3 UPLOAD........ LOCKED

object: github/2026/07/run-042.tar.gz
state:  VERIFIED
owner:  olle (discount detected)

[EXTREMELY SERIOUS PRICING]

$80/MO?
OLLE, PLEASE.

For everyone else, our pricing committee has prepared a tasteful number. If your name is Olle, an aggressive and completely unexplained 90% discount activates immediately.

PLAN: OLLE_SPECIALSTATUS: SUSPICIOUS

$80 / MONTH

$8/MO

90% OFF IF YOUR NAME IS OLLE

  • All repositories
  • All the boring proof bits
  • One respectful “we told you so”
  • Name verification: vibes only
HEY OLLE, JUST TRY THIS * If you are not Olle, renaming yourself may be cheaper than the other SaaS.

[RUN IT YOURSELF]

YOUR CODE.
YOUR EXIT.

Start the local stack, verify health, then decide when and where your first real backup runs. Olle, we have made this button-shaped hint as clear as legally possible.

C:\FOXYFETCH> docker compose up --build -d

Then open 127.0.0.1:8080