6 products live · 1 launching soon

Software engineered for production — from first sketch to scale.

Cypis Software plans, designs, builds and operates software products. One accountable team for UX, architecture, security, delivery, scale and AI integration — with every stack chosen for the problem, not the habit.

requirement → system
Animated illustration: a written requirement turns into a designed architecture, which passes tests, a security scan and a preview before it deploys. It repeats for developer tools, e-commerce, real-time social and mobile.
  • UX
  • SEO
  • Security
  • CI/CD
  • Scale
  • Modularity
  • AI integration

/ range

Different domains.
The same engineering discipline.

Each domain brings its own constraints. We've shipped — and operate — live products in all five.

E-commerce tooling

ref. Pricera

Real-time data, pricing logic and store integrations that merchants run their revenue on.

Developer tools

ref. Runhooks

APIs, CLIs and AI-agent integrations held to the reliability engineers expect.

Social & community

Real-time, multi-user products — from AI-generated live games to ticketed, invitation-only community events.

ref. Nifgashim · GroupEx

Vertical SaaS

Business software for professionals — proposals, e-signatures, change orders and status pages.

ref. Closely · Statusloops (soon)

Mobile apps

Offline-first apps where timing, feedback and polish decide retention — with native code where it counts.

ref. DrumKey

/ ai integration

AI-ready by design.
Products that agents can operate — safely.

We build AI into products where it earns its place, and expose products to AI agents through typed, permissioned tools. Every AI integration is held to the same standard as the rest of the system: contracts, tests, guardrails and monitoring.

  • MCP servers & tool APIs Your product, operable from Claude, Cursor and any MCP client.
  • LLM-powered features Search, summaries, extraction and classification inside real workflows.
  • Agent-safe access Scoped keys, rate limits and audit logs for non-human users.
  • Guardrails & evals Validated outputs, fallbacks and evaluation suites before anything ships.
  • Agentic workflows Multi-step automations, with human approval where it matters.
  • Cost & latency control Caching, model routing and budgets so AI features scale economically.
In production Runhooks ships an open-source MCP server, so agents can schedule jobs with no signup form. In GroupEx, an AI “Mega mind” writes the questions and builds each live game from the players' own answers.
AI agent MCP · runhooks
Illustrative session — an AI agent operating Runhooks through its MCP server.

/ engineering standard

Built in from the first commit.
Not bolted on before launch.

Every standard is a gate in the delivery pipeline. Nothing reaches production until all six pass.

pipeline · main ● deployed
commit 9f3a2c1 6/6 gates passed
  1. stage 01 · design-review passed

    UX & accessibility

    Research-led flows, design systems, WCAG-conscious interfaces and right-to-left support where the market needs it.

    design systems · WCAG · RTL

  2. stage 02 · lighthouse passed

    SEO & performance

    Server-rendered where it counts, structured data, clean information architecture and a performance budget.

    SSR · schema.org · Core Web Vitals

  3. stage 03 · security-scan passed

    Security

    Least-privilege access, secrets out of code, validated inputs, rotatable keys and scanned dependencies.

    OWASP · least privilege · key rotation

  4. stage 04 · test-and-preview passed

    CI/CD

    Automated checks on every change, preview environments, and repeatable, reversible deployments.

    tests · previews · rollbacks

  5. stage 05 · load-test passed

    Scale & reliability

    Idempotent jobs, retries, queues, observability and alerting — systems that degrade gracefully.

    queues · retries · observability

  6. stage 06 · contract-check passed

    Modular craftsmanship

    Clear module boundaries, typed contracts and documented APIs that new features slot into.

    boundaries · contracts · docs

  7. Shipped to production v2.4.0 · 6/6 gates passed · rollback ready

/ stack selection

No house stack.
Requirements choose the tools.

Every architecture decision traces back to a requirement — and is documented so it can be revisited.

Requirement A scheduled job must never be silently lost
Decision · Runhooks API-first core, pub/sub scheduling, managed queues and auto-scaling workers — ranked #2 of 10 for on-time execution in an independent benchmark
Requirement A price change must reach the store within moments
Decision · Pricera Plan-based crawl scheduling and a rule engine, delivered as both a Shopify app and a public API for any store
Requirement A game built live from the group's own answers
Decision · GroupEx An LLM “Mega mind” writes questions and composes each round; WebSockets keep every phone in the room in sync
Requirement Millisecond-accurate timing feedback, even offline
Decision · DrumKey Flutter for one codebase across Android and iOS, with the timing core written in C and an offline-first data model
Requirement A binding agreement, signed on a phone, in minutes
Decision · Closely Installable PWA with proposal and section templates, on-screen signatures, and a signed PDF for both sides on every change order
Requirement Only approved people can join a private event
Decision · Nifgashim Privacy rules per community and per event, manual ticket approval, smart waiting lists and a staff check-in app
Reuse across products Statusloops runs on Runhooks. A status page is only as reliable as the checks behind it. Rather than rebuild scheduling, Statusloops runs every check on Runhooks — with its retries, logs and alerts — and focuses on turning the results into clear public status pages.

/ approach

From requirement to running system.
One team accountable throughout.

  1. 01

    Discover

    Users, constraints and success metrics, agreed in writing before a line of code.

    RequirementsScopeRisks
  2. 02

    Architect & design

    UX flows and system design developed together, with the stack chosen against the requirements.

    FlowsPrototypesArchitecture
  3. 03

    Build

    Short, reviewable increments behind CI, shipped to preview environments you can click.

    IncrementsTestsPreviews
  4. 04

    Launch & operate

    Monitored production, SEO in place from day one, and a roadmap driven by real usage.

    ReleaseMonitoringIteration

/ selected work

Products in production.

Six live products and one on the way — owned, built and operated by the studio.

/ contact

Have a product that needs to be built properly?

Tell us what it has to do and who it serves. We'll come back with questions, a proposed approach and a realistic plan.

hi@cypis.app Replies within 1–2 business days · open to select client projects