SPCBot
Get Started
Before vs. after SPCBot

How an Odoo deployment used to get done

Before SPCBot, every deployment was a manual, multi-hour job that needed an engineer, a terminal, and a lot of luck. Press play below and watch it happen side by side with what SPCBot does instead.

2–3 hours

of manual SSH work, per deployment

Under 3 minutes

fully automated, from a git push

Watch it happen

Both lanes run on the same clock. Play, replay, or step through it yourself.

Before SPCBot: step 1 of 7 — Engineer opens a terminal. After SPCBot: step 1 of 6 — git push.

Before SPCBot

0:00elapsed
Engineer

  1. Engineer opens a terminal

    ~2m

    Every deployment starts the same way — a laptop, a terminal window, and one engineer.

  2. SSH into the server

    ~8m

    Manually connect to the client’s VPS. Full server access is required just to touch one client’s Odoo.

  3. Install Docker & dependencies

    ~35m

    Docker, system packages, and Python dependencies installed by hand — no two setups end up identical.

  4. Configure Odoo from scratch

    ~40m

    odoo.conf, database, filestore paths, and ports — hand-edited, every single time.

  5. Restart services

    ~10m

    The client’s Odoo goes down while the new setup restarts — every update means downtime.

  6. Wait for the server manager

    ~45m

    Something needs the one person with server access. If they’re unavailable, work simply stops.

  7. SSH back in to debug

    ~25m

    No centralized logs — checking an error means another SSH session into the server itself.

2 people involved · every single time

After SPCBot

0:00elapsed
0 people needed — self-service

  1. git push

    ~3s

    A developer pushes code. No terminal session on any server, no server access at all.

  2. Clone repository

    ~15s

    The pipeline clones the repo automatically — the same steps, every time.

  3. Build & validate

    ~55s

    Docker image built and validated automatically. Identical setup on every deploy.

  4. Deploy to server

    ~45s

    Rolled out with a health check — if it’s not healthy, it rolls back automatically.

  5. Health check

    ~20s

    SPCBot confirms Odoo is actually responding before sending it any traffic.

  6. SSL + live

    ~15s

    The new version is live behind HTTPS. A brief restart is covered by a branded maintenance page — seconds, not the hours of a manual update.

0 people required · fully automated

What else changed

Time isn’t the only thing that used to be a problem.

Server access

Developers need full server SSH/root access just to work on one client.

Role-based access, scoped per client and per environment.

Client isolation

A developer working on Client A can see and touch Client B’s data.

Complete isolation — separate database, network, and storage per client.

Audit trail

No record of who changed what, or when.

Every action logged — user, time, and IP address.

Availability bottleneck

Work stops entirely if the one person with server access is unavailable.

Any authorized developer deploys independently from the dashboard.

Change history & rollback

No change history per client, and no way to undo a bad update.

Full deployment history — rollback to any previous version in one click.

Logs & debugging

No centralized logs — checking an error means SSHing into that server.

Live logs and metrics visible in the browser, no SSH required.

Monitoring

Problems are discovered when the client complains.

Automatic Slack, Telegram, or email alerts — before the client notices.

See everything SPCBot automates

Deployments are just the start — explore the full feature set.

Explore FeaturesGet Started Free