Circe Services

Build · Run · Protect · Advise

Software, security and infrastructure, built to order.

Circe Services designs, builds and runs the technical side of your business: internal tools, apps, APIs, phone farms, hardened servers and the websites in front of them. Working systems on infrastructure you own, with the source and the documentation to keep them.

Start a project See all 16 services
You own the code Runs on your server Fixed quotes
Build your stack Pick what you need and watch it come together. Send it to us when it looks right.
YOUR SERVER HARDENED

Drag the diagram sideways to see all of it.

Components
Components
—
Runs on
—
Typical build
—Confirmed in the written proposal after a scope call.

Drops your selection into the enquiry form below.

What we do

Sixteen services, four jobs.

We build systems, run them, protect them and advise on them. Open any line for what is included, what you get at the end, and how long it usually takes. Every service ends with your team able to run it without us.

01Build

New systems and the parts that connect them. Scoped to the job, deployed to your server, handed over with source.

Custom software & internal tools

Dashboards, CRMs, booking systems and back-office tools built around the job your team actually does. PYTHON · NODE · POSTGRES
Includes
  • Discovery of the current process, usually a spreadsheet and a group chat
  • Data model and roles designed with the people who will use it
  • Admin panel, reporting and exports
  • Imports from the tools being replaced
  • Audit log of who changed what
You get
  • Source in your repository
  • Deployed to your server with a runbook
  • Admin training for the team
Typical
Timeline
3–8 weeks
Engagement
Project, then optional retainer
Runs on
One server you own

SaaS products & white-label platforms

Multi-tenant products with billing, roles and your client's brand on top. We run one ourselves. MULTI-TENANT · STRIPE · ROLES
Includes
  • Tenant model, onboarding and plan limits
  • Subscription billing, invoices and failed-payment handling
  • Role-based access and per-tenant branding
  • Usage metering and admin tooling
  • Status page and tenant-level backups
You get
  • A product you can sell under your brand or your clients'
  • Operating runbook and on-call notes
  • A roadmap for the next two releases
Typical
Timeline
8–16 weeks
Engagement
Project + retainer
Runs on
Your servers, one per environment

Websites & landing pages

Fast, static where possible, measured from day one, hosted on something you control. STATIC · CMS OPTIONAL · ANALYTICS
Includes
  • Page plan and copy structure
  • Design in your brand system, or we set one up
  • No heavy frameworks unless they earn their place
  • Forms wired to your inbox or CRM
  • Analytics, search console and basic SEO
You get
  • Source, hosting and DNS in your accounts
  • Lighthouse scores in the 90s at launch
  • A one-page guide to editing it
Typical
Timeline
1–3 weeks
Engagement
Project
Runs on
Static hosting or your server

Mobile & desktop apps

iOS, Android and desktop apps that talk to the same API as the rest of your system. IOS · ANDROID · DESKTOP
Includes
  • Scope to the screens that matter, not an app for everything
  • Shared API with your web systems
  • Push notifications, offline handling and sign-in
  • Store listings, review process and release builds
  • Crash reporting and an update path
You get
  • Store accounts in your name
  • Signed builds and the signing keys
  • Source and a release checklist
Typical
Timeline
8–14 weeks
Engagement
Project + retainer
Runs on
Your API on your server

APIs & integrations

Make your systems talk to each other, and to your partners, with documentation they can actually read. REST · WEBHOOKS · MCP
Includes
  • API design with versioning and authentication
  • Webhooks with retries and signatures
  • Integrations with payments, CRMs, messaging and social platforms
  • Data pipelines and reporting feeds
  • MCP servers so AI assistants can use your tools safely
You get
  • OpenAPI spec and hosted documentation
  • Sandbox keys for partners
  • Monitoring on every integration
Typical
Timeline
2–6 weeks
Engagement
Project
Runs on
Your server

AI agents & automation

Assistants, bots and scheduled jobs that do the repetitive work, with a human in the loop where it counts. LLM · TELEGRAM · WHATSAPP
Includes
  • Chat assistants for customers or staff, grounded in your data
  • Document and inbox processing
  • Content and reporting pipelines
  • Telegram, Discord and WhatsApp bots
  • Guardrails, logging and review queues
You get
  • Prompts, evaluation set and cost reports
  • Clear hand-off points to a human
  • A model choice you can change later
Typical
Timeline
2–6 weeks
Engagement
Project or retainer
Runs on
Your server plus the model provider

02Run

The things that have to stay up. We set them up properly and, if you want, keep running them.

Phone farms

Racks of real devices, each on its own connection, with a control plane and dashboard. Managed, built on-site or software only. REAL DEVICES · PER-DEVICE NETWORK
Includes
  • Rack design, power, cooling and cabling
  • Per-device connections and identity management
  • Scheduling, task queues and health checks
  • Dashboard with battery, storage and last action per device
  • Weekly report in managed mode
You get
  • A rack that reports to one screen
  • Controls your team can use without us
  • A documented replacement procedure for any device
Typical
Timeline
4–10 weeks
Engagement
Managed or Project
Runs on
Our racks or your premises

Hosting, servers & DevOps

Servers set up properly, costs kept down, deployments that are boring. LINUX · NGINX · DOCKER
Includes
  • Provisioning and hardening of VPS or dedicated servers
  • nginx, TLS and zero-downtime deploys
  • CI pipelines and environments
  • Backups with scheduled restore tests
  • Migrations off expensive platforms
You get
  • Infrastructure in your accounts
  • A runbook per server
  • A monthly cost report
Typical
Timeline
1–3 weeks
Engagement
Project or Managed
Runs on
Hetzner, your own hardware, or any cloud

Email & domain infrastructure

Mail that lands. Domains, DNS and deliverability set up once and watched. WORKSPACE · SPF · DKIM · DMARC
Includes
  • Google Workspace or Microsoft 365 setup
  • DNS, SPF, DKIM and DMARC with reporting
  • Transactional email for your apps
  • Warm-up and reputation monitoring
  • Shared mailboxes, rules and offboarding
You get
  • DMARC reports you can read
  • A record of every DNS change
  • Deliverability checked monthly
Typical
Timeline
Days, not weeks
Engagement
Project or Managed
Runs on
Your registrar and your mail provider

Data, analytics & reporting

One place where the numbers agree. Pipelines, dashboards and per-client reports. PIPELINES · DASHBOARDS · EXPORTS
Includes
  • Pulling data from your platforms, ads and payments
  • A warehouse or a well-structured database
  • Dashboards per team or per client
  • Scheduled reports by email or chat
  • Definitions written down so each number means one thing
You get
  • Dashboards your team opens daily
  • Exports your accountant accepts
  • The data model, documented
Typical
Timeline
2–6 weeks
Engagement
Project + retainer
Runs on
Your server or your warehouse

03Protect

Keep what you run safe, get what was stolen taken down, and find out who did it.

Security hardening & monitoring

Harden what you run, know when something changes, and have a plan for the bad day. HARDENING · ALERTS · RESPONSE
Includes
  • Server and account hardening: SSH, firewall, 2FA, key rotation
  • Access review and least privilege
  • Monitoring with alerts that reach a human
  • Backups restored on a schedule to prove they work
  • Incident response plan and a drill
You get
  • A written baseline and the changes made
  • Alerting that reaches the right person
  • A tested restore
Typical
Timeline
1–2 weeks, then ongoing
Engagement
Project + Managed
Runs on
Your infrastructure

Takedowns & brand protection

Leaked content, impersonation and copycat listings removed, with an evidence trail. DMCA · PLATFORMS · EVIDENCE
Includes
  • Monitoring for leaks, impersonation and fakes
  • DMCA and platform-specific takedowns
  • Escalation paths for repeat offenders
  • Evidence collection suitable for legal use
  • Monthly report of what was found and removed
You get
  • Removals logged with dates and proof
  • A standing process instead of one-off firefighting
  • Documentation a lawyer can use
Typical
Timeline
Ongoing
Engagement
Managed
Runs on
Our tooling, your name on the notices

Investigations & intelligence reports

Find out who is behind the false takedowns, the fake accounts or the fraud, and get it in writing. OSINT · ATTRIBUTION · WRITTEN REPORT
Includes
  • Open-source investigation and attribution
  • Analysis of complainant emails, domains and infrastructure
  • Timeline of events with sources
  • Written report for your legal team or platform contacts
  • Recommendations and next steps
You get
  • A report you can hand to a lawyer
  • Evidence preserved properly
  • A clear answer, or a clear statement of what cannot be known
Typical
Timeline
1–3 weeks
Engagement
Project
Delivered as
A document

04Advise

When you need an opinion rather than a build, or a team that can run what was built.

Technical consulting & fractional CTO

A senior technical lead in your meetings without a senior salary on your payroll. ARCHITECTURE · VENDORS · ROADMAP
Includes
  • Architecture and build-versus-buy decisions
  • Vendor and contractor selection
  • Roadmap and priorities
  • Hiring plans and interview loops
  • Monthly review of what shipped
You get
  • Decisions written down with reasons
  • Someone to call when a vendor pitches you
  • A roadmap the team can follow
Typical
Timeline
Ongoing
Engagement
Retainer
Runs on
Your calendar

Audits & second opinions

Code, security, infrastructure or cost: a written review before you commit. CODE · SECURITY · COST
Includes
  • Code review of an existing system
  • Security review with prioritised findings
  • Infrastructure cost review
  • Due diligence on an acquisition or a vendor
  • Plain-English summary for non-technical readers
You get
  • Findings ranked by severity and effort
  • What to fix first
  • An estimate for fixing it
Typical
Timeline
1–2 weeks
Engagement
Project
Delivered as
A document

Team training & handover

Your team runs it after we leave. Documentation, training and, if needed, help hiring. RUNBOOKS · TRAINING · HIRING
Includes
  • Runbooks and admin documentation
  • Recorded walkthroughs
  • Live training sessions for staff
  • Job specs and interviews for technical hires
  • Thirty days of support after handover
You get
  • A team that does not need to call us
  • Documentation that stays current
  • A hiring shortlist, if you asked for one
Typical
Timeline
1–2 weeks
Engagement
Project
Runs on
Your tools
We work in PythonNode.jsPostgresSQLitenginxDockerLinuxCloudflareHetznerStripeGoogle WorkspaceTelegram Bot APIPlaywrightAnthropic & OpenAI APIsSwift & Kotlin

Who we work with

Businesses that run on systems, or should.

Most of our clients are small and medium businesses with more operations than engineers. The common thread is a process that has outgrown the tools it started on.

Agencies & creator businesses

Chat teams, content operations, link tracking and brand protection. We came from here and still run one.

E-commerce & D2C brands

Storefront integrations, order and stock tooling, fraud and takedown casework, and reporting that matches the bank.

SaaS founders

First versions, multi-tenant platforms and the infrastructure to run them without a platform team.

Property & local services

Booking, portfolio trackers, payments and the websites that make the phone ring.

Professional services

Firms running on email and spreadsheets that need one system of record and a way to report from it.

Teams with an inherited system

Something a previous developer built and left. We take it over, document it and make it safe to change.

Selected work

A few things we have built.

Names withheld. References available on request once we have spoken.

  • Multi-tenant chatting platform

    For creator-management agencies: hub, dashboards, pay-per-view scheduling, Telegram bots and per-tenant white-labelling. Runs an agency's whole chat operation from one server.

    SAAS · BOTS · WHITE-LABEL

  • Deeplink and bio-link platform

    Per-profile analytics, in-app-browser escape to a real browser, metadata controls and CRM integration. Built to replace an off-the-shelf link tool that kept breaking.

    LINKS · ANALYTICS · CRM

  • Phone-farm control plane

    Dozens of real devices with their own connections, schedules and health checks, reporting to a single dashboard per rack.

    HARDWARE · SCHEDULING · DASHBOARD

  • Takedown-intelligence investigation

    For a large e-commerce brand being hit with false takedown requests: identified who was behind them from two complainant emails and delivered a written report for the client's legal team.

    OSINT · REPORT

  • Property portfolio tracker

    Units, tenancies, payments and maintenance for a rent-to-rent operator, with a separate view for the short-let side of the business.

    INTERNAL TOOL · PAYMENTS

  • Contract and invoicing workflow

    E-signature page, commission invoicing and automated payment chasers for a management agency, replacing a folder of PDFs and a reminder spreadsheet.

    AUTOMATION · E-SIGN

  • Booking site for a mobile service business

    Quotes, bookings and payments for a mobile valeting company, hosted and handed over with a guide to editing it.

    WEBSITE · BOOKINGS

Several of these started as internal tools for our own agency and were later rebuilt for clients.

Phone farms

Marketing automation on real hardware.

Platforms can tell an emulator from a phone and a shared IP from a home connection. A rack of real devices, each with its own connection, behaves like real users because it is real hardware. Every device reports in, runs its schedule and appears on one dashboard with its battery, storage and last action.

  • ManagedWe host the rack, run your schedules and send a weekly report. Monthly fee per device.
  • BuiltWe build the rack on your premises, install the control plane and train your team. One-off project.
  • Software onlyYou already have the devices. We supply the control plane and dashboard and connect them.
RACK A · 24 DEVICES —
Online
—
Tasks today
—
Attention
—
Loading example rack…

Example rack with simulated activity. Your dashboard shows your devices.

How we work

Scope, quote, build, hand over.

Four steps, in this order, every time. The proposal is never longer than two pages and nothing is billed before it is signed.

  1. 01

    Scope call

    Thirty minutes. You describe the problem; we ask about constraints, existing systems and who will run it afterwards.

  2. 02

    Written proposal

    A fixed price and timeline for a fixed scope, or a day rate for open-ended work. What is in, what is out, what you provide.

  3. 03

    Build in the open

    A staging URL from the first week, progress updates on a schedule you choose, and scope changes priced before they are built.

  4. 04

    Handover

    Source in your repository, a deployment runbook, admin training for your team. A retainer afterwards if you want one.

Engagement

Three ways to work with us.

Pick the shape that fits the work. Every one starts with the same scope call and a written quote.

Project

For a defined build with a clear finish line: a tool, an API, a site, a rack, a report.

  • Fixed scope, fixed price, fixed timeline
  • Staging URL and weekly updates
  • Handover with source and runbook
  • 30 days of fixes after launch

Quoted per project

Retainer

For teams that want ongoing engineering or a fractional technical lead without hiring.

  • Reserved days each month, used how you choose
  • Priority response on anything we built
  • Monthly review of what is next
  • Cancel with one month's notice

Monthly, by days reserved

Managed

For systems you would rather we ran: phone racks, servers, email, monitoring, takedowns.

  • We host, patch, monitor and report
  • Agreed response times in writing
  • Weekly report, monthly review
  • Everything exportable if you leave

Monthly, by device, server or scope

Questions

The things people ask first.

Who owns the code?

You do. Everything written for you is yours on final payment, in a repository you control. We keep nothing back and there are no licence fees for your own software.

Where does it run?

On infrastructure you own or rent in your name. We set it up, document it and hand over every credential. If you want us to run it afterwards, that is a managed engagement, and everything stays exportable.

Can you take over something another developer built?

Yes. It starts with an audit so we both know what is there, then a short plan to make it safe to change. We will tell you if it is cheaper to rebuild than to rescue.

What is the smallest job you take?

A day. An email setup, a review, a fix. There is no minimum beyond a written quote, and small jobs are often how larger ones start.

Do you work with agencies and creators?

Yes. Circe started in creator management and still runs its own agency, which is where the phone-farm tooling, the chat platform and the takedown casework come from. The services on this site are open to any business.

What stack do you use?

Mostly Python and Node, Postgres or SQLite, nginx, and plain HTML, CSS and JavaScript on the front end; Swift and Kotlin for native apps. We work inside whatever your existing systems require, and we will say so if something you have asked for is not a good fit.

Do you sign NDAs?

Yes, yours or ours, before the scope call if you prefer. Everything you tell us about your business stays between us regardless.

Where are you based?

The UK, working remotely with clients wherever they are. Scope calls and support run on UK hours; managed services have agreed response times that are written into the contract.

How is pricing set?

Fixed price for fixed scope. A day rate for open-ended work. A monthly fee per device, server or scope for managed services. A written quote always comes before any work, and changes to scope are priced before they are built.

What happens if we stop working together?

You keep everything: source, servers, accounts, documentation. Managed services wind down over a notice period with a handover, and we stay reachable for questions after that.

Start a project

Tell us what you need.

A few lines is enough. Say what the problem is, what you have already, and when you need it. We reply within one working day with questions or a time for a scope call.