Services

How we engage

We keep commercial terms simple. Pricing and availability are discussed on inquiry; there are no public rate cards.

Model	Best for
Fixed-scope project	A defined outcome: design doc, service hardening, pipeline build, or a bounded feature with clear acceptance criteria.
Hourly / time & materials	Exploratory work, spikes, or scope that will move as you learn.
Monthly retainer	Ongoing access: architecture guidance, code review, mentoring, and a bank of hands-on hours for the problems that surface each month.
Part-time embed	We join your team at 20–40 hours per week as a senior engineer; useful when you need ownership inside an existing codebase without a full-time hire.

Typical floors: project engagements usually start around two weeks or 40 hours; retainers and embeds generally start at one day per week (about 20 hours monthly for retainers). We will tell you quickly if a brief is too small to be worth your budget or ours.

What we do

Web, creative, and interactive design

We design: web and creative work, character designs, UI/UX, and interactive experiences. The Arathyll site you are reading is our design end to end (visual system, navigation, and content structure) as well as our engineering.

Example work: product identity and creative direction, character design, interactive site UX, and the Dev / Betwixt / portal shells on this nexus.

Live backends and online services

We architect and build services meant to stay up when players or customers show up. Caching layers, horizontal scaling, deployment patterns, and the operational habits that keep incidents rare and recoverable.

Example work: currency and inventory services, session and matchmaking adjacency, API gateways, and the glue between game clients and persistent state.

Netcode, multiplayer, and simulation

We advise on and implement networked architectures that respect latency, cheating, and rollback. Our game work targets deterministic simulation and GGPO-style rollback on a custom ECS engine; we bring that mindset to whatever stack you run.

Example work: authority models, snapshot and prediction strategies, interest management, and production debugging when desyncs appear under load.

Developer infrastructure

We build the workflows teams actually use: CI/CD, artifact pipelines, environment promotion, and observability that shortens incident response instead of adding dashboard noise.

Example work: greenfield CI/CD pipelines, Datadog enrichment for faster triage, and internal platforms that remove manual hours from weekly ops.

Greenfield architecture and delivery

We help teams go from first commit to something shippable: service boundaries, data models, API contracts, and an execution plan that matches your team size.

Example work: new microservice suites, internal tools, and game backend foundations before launch traffic arrives.

Legacy modernization and hardening

We are comfortable inheriting code that already earns revenue. We trace failure modes, reduce operational risk, and improve testability without a rewrite fantasy unless one is truly warranted.

Example work: billing and provisioning systems (including prior work at Datto), legacy HTTP layers on live game services, and incremental refactors that keep shipping during migration.

Data platforms, billing, and integrations

We have shipped financial and operational systems where correctness matters. Warehousing, middleware, SSO integration, and the unglamorous integrations that keep finance and support from paging you at midnight.

Example work: Zuora/Salesforce middleware, revenue reporting pipelines, DNS and provisioning platforms, and customer-facing portals.

Engine-adjacent tooling and pipelines

We build tools that fit how your team already works: exporters, validation, content pipelines, and agent-friendly developer utilities. We maintain Wordkeep and related tooling in the Betwixt monorepo and apply the same pragmatism to the repos we join.

Example work: build and content automation, static analysis hooks, and small services that remove recurring manual steps.

Technical leadership, mentoring, and review

We run design discussions, code reviews, and pairing sessions that level up the team around us. We have mentored interns and senior engineers alike and we are direct without being theatrical about it.

Example work: staff augmentation with ownership, architecture reviews before a major bet, and helping hiring managers calibrate senior backend bar-raisers.

How we work

Process: send a short brief through contact. We schedule an intro call, then return a scoped proposal with timeline, assumptions, and engagement model. No multi-week procurement theater unless your org requires it.

Delivery: engagements are founder-led; you work with the person who scoped the work. If we bring in specialists, we remain accountable for the outcome.

Location: remote-first, Americas-friendly hours for calls and overlap. On-site visits are possible for the right project by arrangement.

Stacks and environments

We lead with Rust, C++, C#, and TypeScript on the application side; AWS, Docker, PostgreSQL, and Redis are common in our deployments. We have deep experience with Windows services, .NET, Datadog, CI/CD (GitHub Actions and friends), and SaaS integrations (Zuora, Salesforce, Okta). Game-facing work includes custom engines, Unreal-adjacent online services, and ECS-driven simulation.

We choose tools for maintainability and team fit, not résumé padding.

How to start

Tell us what you are building, what is breaking or at risk, and when you need help. Include stack, team size, and any hard deadlines.

Contact

Start a conversation with a short brief and timeline.
Portfolio

Case studies and open repos: engine, netcode, tooling, and platforms.
Availability

Current capacity notes and how quickly we can start.