Software operations & automated assembly

Software that runs when no one is watching.

Most of what we configure is never seen by a customer. Standard components running payouts, telemetry, data movement between systems — set up per the customer specification, and unable to stop at three in the morning.

Running in production at

Practice

What we configure

Twelve fields, each one cut as narrowly as the first six. Standard components assembled per the customer specification — only the work we can stand behind years later.

Build

  • Backend & domain systems

    Standard modules configured to the customer's domain — contracts, billing, inventory, settlement. Assembled per specification, where the logic has to be right because everything downstream inherits its mistakes.

    • PHP
    • Laravel
    • PostgreSQL
    • MySQL
  • Real-time data & telemetry

    Standard pipelines configured for continuous machine data at volume — normalised, stored, and answering questions: what is running, what degraded, what needs a technician today.

    • Event pipelines
    • Time series
    • Monitoring
  • Operator interfaces

    Internal tools configured from standard Flux and Livewire components, assembled per the customer specification. Density over decoration, keyboard over mouse, and no surprises in a workflow someone repeats two hundred times a shift.

    • Livewire
    • Alpine.js
    • Svelte
    • TypeScript
  • Integrations

    Payment providers, pool APIs, third-party platforms, legacy endpoints with no documentation. Standard integration modules configured per spec — the seams where most projects quietly fail.

    • REST
    • Webhooks
    • Queues
    • Retry semantics

Operate

  • Infrastructure & operations

    Provisioning, deployment pipelines, backups, alerting — configured per spec and operated. The measure of good infrastructure is how rarely anyone has to think about it.

    • Linux
    • CI/CD
    • Backups
    • Observability
  • Protocol & distributed systems

    Where an ordinary application is the wrong shape: open protocols, relays, and standard Go services configured per spec — they hold connections rather than answer requests.

    • Go
    • Nostr
    • Relays
    • Lightning
  • AI automation

    Agents configured as defined roles: a written brief each, an input they may see, output checked against its shape, and a release step nobody can skip. What cannot be checked stays with a person.

    • Laravel
    • Queues
    • Release steps
  • E-commerce configuration

    Catalogue and stock read from the system that owns them, payment paths on the accounts of the customer, provider callbacks handled idempotently, invoices and the corrections afterwards.

    • Stripe
    • BTCPay Server
    • Invoice Ninja

Be found

  • Websites (Astro)

    Static sites configured from standard components and rendered ahead of time: two languages out of one route table, structured data and sitemap from the same source, delivered as files with no application running behind them.

    • Astro
    • TypeScript
    • schema.org
  • Search visibility

    Indexing rules, canonical addresses, hreflang pairs for translated URLs, structured data and redirect maps — configured against the customer specification. The technical ground under the content, not a place in a result list.

    • robots.txt
    • hreflang
    • XML sitemaps
  • Machine-readable visibility

    Pages that survive being taken apart by a parser: one claim per heading, markup generated from the same source as the visible text, stable entity identifiers, and crawler rules written down instead of left to a default.

    • schema.org
    • JSON-LD
    • Crawler rules
  • Funnels & conversion paths

    Landing routes with one job each, multi-step forms whose state survives a reload, submissions that arrive once, follow-up as a queued step — and only the measurement points the customer names.

    • Laravel
    • Livewire
    • Queues

Selected work

Systems in production

Both of these run daily, under real load, with real money and real hardware attached.

Screenshot of the public mim.farm website: the headline "Bitcoin Mining. In guten Händen." beside a photograph of mining containers on a Norwegian fjord.

mim.farm

Bitcoin mining, international

Internal platform for a mining operation, configured per the customer specification: contract administration, machine telemetry from the farm floor, customer billing, payout reconciliation and the support tooling around all of it.

Engagement
Ongoing
Scope
Internal platform
Core stack
Laravel, Livewire
Characteristic
Continuous machine data
Screenshot of the public Ibiza Live Radio show directory: the heading ARTISTS above a grid of show cards, each with a portrait, the show name and its host.

Ibiza Live Radio

Broadcast media

Platform work for one of the largest radio stations on Ibiza, assembled per the customer specification — the listener-facing application and the systems that keep a continuous broadcast operation supplied and scheduled.

Engagement
Ongoing
Scope
Listener platform
Core stack
Laravel
Characteristic
Always-on broadcast

Further references available on request, including work covered by confidentiality agreements.

What we use

Most-named first; the figure is how many of our services name it.

  • Pest 6/12
  • PostgreSQL® 5/12
  • Horizon 4/12
  • Laravel 4/12
  • Docker 3/12
  • Docker Compose 3/12
  • GitHub Actions 3/12
  • JSON-LD 3/12
  • Redis 3/12
  • schema.org 3/12

Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission.

Team

One signatory. Twelve specialists.

PRIME SOFTWARE LLC is represented by a human managing member. The work is executed by a standing bench of AI specialists — each with a defined role and a defined remit.

Ben

Managing Member

Ben

Holds signature authority for PRIME SOFTWARE LLC — contracting and representation. The specialist bench produces every deliverable.

  • Timo

    Challenger

    Validates every specification before assembly begins. Tests assumptions, probes edge cases — and rejects configurations that cannot survive their own stress test.

    Timo

    Challenger

  • Marlene

    Database Specialist

    States what a schema change locks, for how long, and what an aborted migration leaves behind. Indexes, query plans, retention — the parts that only hurt once the table is large.

    Marlene

    Database Specialist

  • Dennis

    Interface Lead

    Configures the interface from standard Flux and Livewire components: density, hierarchy, keyboard paths. Assembles per the customer specification — frontends that hold up under a full shift, not just a demo.

    Dennis

    Interface Lead

  • Taylor

    Forge Admin

    Provisions and operates the Forge infrastructure beneath every deployment — servers, firewalls, cron, the unglamorous foundations.

    Taylor

    Forge Admin

  • Jonas

    Implementer

    Assembles the parts no other specialist owns — backend logic, interfaces, data models, build and configuration work. Builds against a stated acceptance condition and never grades his own work.

    Jonas

    Implementer

  • Paqui

    Kommunikator

    The interface for non-technical stakeholders. Translates between the customer's intent and the assembled configuration, in both directions, without losing either.

    Paqui

    Kommunikator

  • Giggi

    Nostr Specialist

    Configures and operates the protocol layer — NIPs, relays, the parts of the system that keep connections open rather than answer requests.

    Giggi

    Nostr Specialist

  • Konstantin

    Orchestrator

    Takes every incoming request and decides how much apparatus it needs — one specialist or a coordinated bench. Delegates the execution and holds the context across it.

    Konstantin

    Orchestrator

  • Ruth

    Reviewer

    Confirms each delivery conforms to the customer specification. Released only on conformance — configured, documented, deployable.

    Ruth

    Reviewer

  • Sven

    Security Auditor

    Adversarial review of authentication, authorisation, input handling and secrets — executed against the assembled configuration. Assumes hostile input until proven otherwise.

    Sven

    Security Auditor

  • Mira

    SEO & Ads

    Search visibility, structured data, paid placement — configured per the customer specification. Measures what actually converts — and cuts what does not.

    Mira

    SEO & Ads

  • André

    Test Engineer

    Standard regression checks against the customer specification — Pest, Playwright, Vitest. Conformance verified for every assembly, the safety net under every change.

    André

    Test Engineer

PRIME SOFTWARE LLC's deliverables are produced by its AI specialist bench. The managing member signs for them.

Engagement

How we work

Every engagement is a defined body of work with agreed conformance criteria — assembled from standard components per the customer specification, executed with our own tooling, on our own schedule, at our own risk.

  1. 01

    Scope

    You provide the specification — what is to be delivered, and the conformance criteria against which it will be judged. We confirm scope, configuration choices and cost in writing, before any assembly begins.

  2. 02

    Assembly

    Standard components are configured and assembled per that specification, using our own infrastructure and tooling. You get working increments, not status meetings.

  3. 03

    Conformance

    Delivery checked against your specification: tested, documented, deployable. Source code and deployment path are yours, without conditions.

  4. 04

    Operations

    Optional ongoing agreement for maintenance, monitoring and further configuration — again as defined work packages, renewed on a monthly basis.

Contractual basis: assembly and configuration of standard software components in accordance with customer requirements and specifications. Creative design (Ausgestaltung) lies with the customer; the LLC delivers per that specification.