Oryntis
Dawn clouds over a moorland ridge (illustrative generated image)

Apps · web · cloud orchestration · Bradford

Software with room to breathe, and a sky that holds it up.

Oryntis designs, builds, publishes and supports mobile apps and websites, and arranges the cloud underneath them so it stays calm, observable and affordable. Light on the surface; orderly all the way down.

Illustrative generated image.

Orchestration, plainly

Three layers, one weather system

Surface

What people touch

Mobile apps, websites and admin tools. Designed so that the first screen makes sense and every action gives clear feedback, even when the network is slow.

Middle air

What connects it

APIs, sign-in, notifications, payments and integrations with services you already use. Mapped and documented so nobody depends on memory.

High altitude

What keeps it aloft

Hosting, environments, automated deployments, backups, monitoring and cost visibility. Quiet when healthy, loud when it should be.

Services

Everything circles the product

We work across the whole lifecycle, but every service exists to keep one thing healthy: the product your people use. Pick any orbit to read more.

Tool one · illustrative

Compose an environment

Choose the parts of your product and how many environments you want. The composer sketches the layout and lists what each environment needs. A starting point for a conversation, not a design.

Components
Environments

    Soft overlapping veils of apricot, rose and blue (illustrative generated image)
    Illustrative generated image.

    Mobile and web

    Light interfaces on solid ground

    The best apps feel weightless because a great deal of careful work sits underneath. We build iOS and Android apps, natively or cross-platform, and websites from public pages to logged-in tools.

    Because we also arrange the cloud side, we design both together: an app that knows how to behave when an API is slow, a website that deploys in minutes without anyone holding their breath, a database that is backed up and restorable, not just backed up.

    • Native and cross-platform apps
    • Websites, portals and internal tools
    • APIs and integrations
    • Hosting, deployment pipelines and backups
    Apps and cloud in detail

    Experience design

    Clarity is a kind of weather

    Listen

    Conversations with the people who use and support the product.

    Map

    Journeys, including the moments people hesitate or give up.

    Prototype

    Clickable designs tested with a handful of real users.

    Systemise

    Components, states, wording and accessibility rules, documented.

    Accessibility to WCAG 2.2 AA is a design input, including reduced motion. The soft drifting on this site stops if your device asks it to.

    How we design

    Signs you need orchestration

    Five forecasts we hear often

    Common situations, described generally. If one sounds familiar, the fix is usually less dramatic than it feels.

    Deploying is a ceremony

    Releases happen late on a Friday with someone copying files by hand and everyone else holding their breath. An automated pipeline with a staging step turns that into a routine button press, any day of the week.

    Nobody knows what the bill is for

    The monthly cloud invoice grows and no one can say which part of it is the website, which is the app and which is a test server left running since spring. Tagging and a plain-English summary make it legible again.

    Backups exist, probably

    There is a backup setting switched on somewhere, but nobody has ever restored from it. A scheduled restore test, written up in a short runbook, turns a hope into a known quantity.

    One person holds the keys

    Access lives in a single developer’s account or memory. Moving accounts into your organisation’s name, with sensible roles and multi-factor sign-in, removes a quiet but serious risk.

    Problems are reported by customers

    You hear about an outage from an email rather than an alert. Basic health checks and error tracking, routed to the right people, mean you usually know first.

    Tool two

    What does 99.9% actually mean?

    Availability targets sound similar and differ enormously. Translate a percentage into the downtime it allows, so you can choose a target worth paying for.

    Drag to compare common targets: 95%, 98%, 99%, 99.5%, 99.9%, 99.95%, 99.99%, 99.999%.

    Per week
    Per month (30 days)
    Per year

    Publishing

    Releases that land softly

    1. PrepareStore listings, screenshots, privacy declarations and release notes written in plain English.
    2. StageEvery release runs in a staging environment that mirrors production before anyone else sees it.
    3. SubmitApp Store and Google Play review, with reviewer notes and test accounts ready.
    4. PhaseGradual rollout where available, watching error reports as it widens.
    5. ReverseA written, rehearsed rollback for web and API changes.

    Delivery standards

    Forecasts you can rely on

    Written scope

    Purpose, users, inclusions, exclusions and risks agreed before work starts.

    Weekly note

    Done, next, blocked, and decisions we need from you.

    Fortnightly builds

    Something working you can open yourself.

    Infrastructure as code

    Environments described in files, reviewable and repeatable.

    Tested restores

    Backups are proven by restoring them, on a schedule.

    Your accounts

    Cloud, store and code accounts in your organisation’s name.

    All delivery standards

    Tool three · illustrative

    Backup retention planner

    Decide how far back you could restore, and roughly how much storage that needs. Enter how many daily, weekly and monthly copies to keep.

    Support

    Weekday care, written down

    Fixes, operating-system updates, dependency upgrades, certificate renewals and cloud housekeeping. Requests are read Monday to Friday, 09:00–18:00 London time and prioritised by impact. We do not run a 24-hour service and will not imply one; we help you set up alerts that reach your own team out of hours.

    Support and request form

    Clear answers

    Which cloud providers do you work with?

    Mainstream providers with UK or EU regions, chosen with you. We prefer arrangements that another team could take over easily, and accounts always sit in your name.

    Can you take over existing hosting?

    Yes, after a short review. We document what exists, point out risks, and propose changes in order of importance.

    Do you guarantee uptime?

    We do not publish uptime guarantees. Availability depends on design, budget and providers; we help you choose a sensible target and build towards it.

    How do we begin?

    Send a short description through the contact page. We reply in working hours.

    Ready to clear the sky?

    Start a conversation