Skip to content
Computese home
Menu

Services

Ten service lines, one engineering team. Start with one or combine several: the people who build your systems are the people who run them, secure them and reply when you email.

Talk to an engineer

07

Cloud transformation

Workloads moved to containers and cloud platforms with a landing zone, a pilot and a way back at every stage.

  1. Assess
  2. Landing zone
  3. Pilot
  4. Migrate
  5. Operate

Every stage keeps a way back

Red Hat OpenShiftKubernetesAWSAzure

08

Data platform

Pipelines, a governed lakehouse and metrics your teams can trust, built so your own staff can run them.

  1. Sources
  2. Ingest
  3. Model
  4. Serve
PostgreSQLApache KafkadbtPower BI

01

Web design & development

Fast, accessible marketing sites and web applications, designed and engineered by one team.

03

SEO

Technical SEO, migrations and content that protect the traffic you have and earn more.

Ccomputese.com › blog

Best practices for secure coding

A working checklist for input validation, secrets and dependency hygiene, written for small teams.

TitleDescriptionCanonicalSchema

04

IT support

An engineer on the line when a laptop, account or inbox stops working, and a plan so it happens less.

  1. Reported
  2. Triaged
  3. Fixed
Hours
Mon–Fri, 9:00–17:00 ET

02

Hosting & maintenance

Managed hosting with patching, proven backups and monitoring, run by engineers.

  • Updates applied
  • Backups verified
  • Uptime monitored

Example status strip, 30 days

05

Security testing

Scheduled vulnerability scanning and manual penetration tests of your networks, apps and cloud, with findings ranked by real risk.

  • HighTLS 1.0 still accepted on the mail server
  • MediumAdmin login reachable from the internet
  • LowMissing security headers on two sites

Example findings from a scheduled scan

06

Integrations

CRM, accounting, e-commerce and internal systems connected, so data is entered once and stays in step.

09

Custom software development

Business platforms, SaaS products, portals and internal tools, with the APIs and back ends behind them, built and run by one team.

Depends onWhen it fails

  • Payment providerRecovers
  • Email providerRetries
  • AI modelFails over
  • Signing serviceFails closed

Example fallback plan, one answer per outside service

10

AI & automation

Workflows, assistants and agents that use AI where a step needs judgment, with a person approving what matters.

Invoice from the shared inboxProposal

  • SupplierMatched to a known record
  • TotalLine items add up
  • Purchase orderFound, amounts match

Waiting for the finance lead to approve

Example: the model reads, a person approves

An IT engineer's kit laid out on a pale grey surface in a precise grid: a small network switch, a fibre patch cable with an orange connector, an NVMe drive, a hardware security key and a closed laptop.

One partner, the whole estate.

Ten lines, one operating model. The engineers who build a system are the ones who run it, secure it and help it grow, so nothing is lost at a handover between vendors.

The ten service lines as one operating model. Build: web design and development, custom software development, integrations, AI and automation, cloud transformation and data platform, run on infrastructure as code, reviewed pull requests and tested rollback. Run: hosting and maintenance, and IT support, with patch windows, restore drills and one ticket queue. Protect: security scanning, ranked with CVSS, EPSS and KEV, cloud posture checks and re-tests. Grow: SEO, through crawling and indexing, Core Web Vitals and structured data. What running, protecting and growing teach feeds the next build.

Fig. 1 One team across the lifecycle. Cloud and data lead the build; every line hands over to the next without a new vendor.

Start from the problem.

Tell us what is going wrong, not which service you need. Each of these has a small, fixed first engagement that ends in a written result, whether or not we do the rest.

What you get back.

The work ends in documents the person who has to act can act on. Three samples of the format, on demo data.

  • 05Security finding

    Sample

    HighOn the CISA KEV list

    Path traversal in an outdated Apache web server

    Asset
    portal.example.com
    Scores
    CVE-2021-41773, CVSS 3.1 7.5, known exploited
    Evidence
    Apache/2.4.49 in the banner; traversal confirmed with a harmless read
    Impact
    Files outside the web root can be read from the internet
    Fix
    Upgrade to Apache 2.4.51 or later; hide the version banner
    Owner
    Web team, due in 7 days
    Closed when
    The same request fails after the fix, re-tested

  • 02Monthly service report

    Sample

    example.com, one month of hosting

    Updates
    Core and 14 plugins updated; 1 held back, with a note
    Backups
    Every scheduled run completed; off-site copy verified
    Restore test
    Restored to staging in 18 min, against a 60 min target
    Uptime
    99.98%, measured from 3 regions
    Certificates
    Renews automatically in 41 days
    Incidents
    One P2: checkout error after an update, rolled back
    Next
    Replace one abandoned plugin

  • 08Metric definition

    Sample

    Active customer

    Definition
    At least one paid order in the last 90 days, refunds excluded
    Owner
    Head of Sales
    Grain
    One row per customer per day
    Built from
    orders, customers, refunds
    Tests
    Unique, not null, fresh within 6 hours
    Used in
    Sales dashboard, month-end pack, churn API

Examples on demo data, not client work. Values are illustrative.

Proof you can check.

Things you can open, test or ask about today, without taking our word for anything.

  • Running in production

    Minute Notary

    A legal services platform, designed, built and maintained by our team.

    minutenotary.ca

  • Test this page

    Speed and accessibility

    Server-rendered, built to WCAG 2.2 AA and to Google's good Core Web Vitals thresholds. Run the test yourself.

    PageSpeed Insights

  • A migration in public

    This website

    Moved off WordPress with every blog URL kept, and every other change a recorded 301 or 410.

    How we migrate →

  • Certified engineers

    AWS, Azure and Google Cloud

    Solutions architect and security certifications, held by the engineers who do the work. Ask which ones matter for your project.

We also run smaller platforms: GoodCleaner and ViaOttawa.

In their words.

A selection of our Google reviews, word for word. Every review is on Google Maps.

5.0 out of 5 on Google

Google rating,

Read every review

  • “Remy saved my business! Seriously, he's got this awesome combo of tech wizardry and genuine care. Thanks a ton, Remy. You're a lifesaver!”

    Tong V., Google review

  • “Trustworthy IT support at a competitive price. The installation process was Amazing :) Thankyou for the Professional service :)”

    Neethu K., Google review

  • “Excellent and efficient service. Highly recommended! Will be using this service again in the near future.”

    Charleen V., Google review

  • “Great service and reliable partner. Highly recommended”

    Tony T., Google review

How we work, whatever the line.

The engineering habits that hold across all ten services.

  • Everything as code, everything reviewed.

    Infrastructure, pipelines and configuration live in Git. Every change is a pull request that someone else approved.

  • Least privilege by default.

    Named accounts, multi-factor authentication everywhere, access granted per role and removed when the work ends.

  • A way back from every change.

    Staged releases, rehearsed cutovers and rollbacks that have been tested rather than assumed.

  • Observable from the first day.

    Metrics, logs and alerts arrive with the system, not after its first incident.

  • Written handover.

    Diagrams, runbooks and decisions documented, so your team never depends on ours to understand its own systems.

  • Your accounts, your data.

    Domains, repositories and cloud accounts stay in your name. Client names stay private, always.

Three ways to work with us.

Pick by how settled the scope is. The proposal recommends one and says why.

Fixed price

ScopeAgreed in writing before work starts

BillingOne price for that scope

Best forDefined projects: a website, an assessment, a migration stage

Time and materials

ScopeSet by priority and adjusted as you learn

BillingBilled for the time used

Best forOngoing improvement, support and discovery work

Dedicated team

ScopeYour roadmap, worked by engineers assigned to you

BillingA monthly rate per engineer

Best forLong programs such as a platform migration

Before you sign.

Do you publish prices?

No, because scope sets the price and no two estates are alike. Every first engagement is quoted in writing before it starts, and the quote lists what is included and what is not.

Do you work outside business hours?

Yes. Cover outside business hours is arranged in the agreement. Support requests follow default reply targets by priority, from 1 hour when the business has stopped.

Can you work alongside our IT team or another vendor?

Yes. Your team can keep day-to-day ownership while we take escalations, projects or a single service line. Who does what is written down before work starts.

Can we start small?

Yes. Every service line has a small, fixed first engagement that ends in a written result you keep, whether or not we do the rest.

Which tools will you use?

Tools from our approved list only: commercial software under its licence, or open source under a standard licence, never cracked or unlicensed. Where your existing platform works, it comes first.

Who does the work?

Engineers, from the first email. The people who scope the work are the people who build it and run it.

Start with a conversation.

Tell us what you run and what is getting in the way. You get a reply within 24 hours.

Talk to an engineer
Email
support@computese.com
Hours
Mon–Fri, 9:00–17:00 ET
Closed on statutory holidays
Office
110 Place d'Orléans Dr
Ottawa, ON K1C 2L9