Skip to main content
Our services

Eight services. Most firms need two or three.

For organizations that want infrastructure they can audit, retain and eventually run without us. Pick the one that is biting you, or book a scoping call and we will work out where to start.

Service · 01

IT Operations

Patch windows agreed in advance, restores that are actually tested, and runbooks written before the outage rather than during it. Monitoring you can read without a dashboard PhD, and tickets that close with documentation rather than the word "fixed".

Open service detail

We operate IT the way ops engineers do at companies that take uptime seriously: written runbooks, change management with rollback paths, monitoring you can interpret without a dashboard PhD, and tickets that close with documentation, not just "fixed."

Capabilities · 6 areas
  • 24/7 monitoring with alert routing tuned for your team's actual on-call hours
  • Patching cadence + change windows documented in advance, never a surprise
  • Backup + tested restore procedures (the test is the part most vendors skip)
  • Disaster-recovery runbooks specific to your stack, rehearsed annually
  • Cloud cost discipline — we'll flag the $400/mo orphaned NAT gateway
  • Help desk that documents the answer once, not the same answer ten times
Who we work with

Practices and small businesses with 5–100 staff whose IT is currently "the person who's good with computers" plus a Microsoft 365 reseller.

Sample engagement

A 15-person law firm handed off the IT function from a departing partner. We took over Microsoft 365 admin, rebuilt the patch cadence, wrote three runbooks (network down, M365 outage, ransomware), and migrated their backups to a tested off-site target. 90-day handoff to a half-time IT coordinator.

Service · 02

Disaster Recovery

Recovery posture engineered to be tested, not just documented. We design backup + restore + failover so the procedure on paper matches the procedure under pressure — and we rehearse it on a cadence that catches drift before an incident does.

Open service detail

DR plans that don't get rehearsed are theater. We design the recovery procedure first, the backup schedule second, and we run live restore rehearsals on a cadence that matches the regulatory and contractual posture of the business. The test is the deliverable; the documentation is the artifact.

Capabilities · 7 areas
  • Recovery-time + recovery-point objectives written down per workload, not assumed
  • Backup strategy designed for the actual restore path — backups you can't restore from are a liability, not an asset
  • Cross-region / off-site replication tuned to threat model, not a vendor's default tier
  • Live restore rehearsals on a cadence the practice can sustain — typically twice yearly
  • Failover runbooks rehearsed under the conditions on-call would actually face
  • Compliance-grade evidence packets for carriers, regulators, and downstream client reviews
  • Tabletop incident exercises with the people who'd actually be in the room
Who we work with

Practices and small businesses that have outgrown "we have a backup somewhere" and need a recovery posture that survives a malpractice carrier review, a state-bar audit, or a HIPAA OCR letter.

Sample engagement

A specialty practice's annual DR rehearsal exposed that their last-known-good backup was 11 days stale and the documented restore procedure referenced an admin who'd left two years prior. We rebuilt the backup target, rewrote the restore runbook against the current stack, and ran a tested restore that completed inside the documented RTO.

Service · 03

Cyber Security

Defense sized to what would actually hurt you: threat modeling first, then endpoint defense, then all four email authentication records — SPF, DKIM, DMARC and MTA-STS — properly tuned. Without the enterprise theater you cannot operate.

Open service detail

Most small organizations don't need a SOC; they need correctly-configured defaults, a written incident-response plan, and someone whose phone rings when the canary trips. We design the posture that matches that reality — and produces evidence regulators, carriers, and clients are starting to ask for.

Capabilities · 7 areas
  • Threat modeling — what would actually hurt us, vs. checklist theater
  • Endpoint defense (EDR + DNS + DLP) sized to staff count, not seat-license fantasies
  • Email authentication: SPF, DKIM, DMARC, MTA-STS — all four, properly tuned
  • Penetration testing on the surfaces that matter (web app, internal AD, BYOD)
  • Compliance audits + evidence packets for SOC 2, HIPAA, state-bar, NIST CSF
  • Phishing simulation tuned to the lures targeting your industry, not generic
  • Incident-response retainer — we'll be the people you call at 3am
Who we work with

Organizations whose clients, regulators, or insurers are starting to ask pointed security questions. Law firms, healthcare practices, RIAs, journalism orgs, advocacy nonprofits.

Sample engagement

A regional medical practice failed a malpractice carrier renewal questionnaire on three controls. We documented the existing controls, remediated the three gaps (MFA on M365 admin, encrypted backups, written WISP), and produced an evidence packet the carrier accepted. Next renewal sailed through.

Service · 04

Artificial Intelligence

Practical AI integration that solves a real bottleneck — not AI for AI's sake. We help you identify where machine learning earns its keep, build it cleanly, and avoid the failure modes that have made "AI rollout" a synonym for "vendor lock-in" for many organizations.

Open service detail

We start with the question "what would a 30% improvement on this specific workflow be worth?" and work backward. If the answer is "a tool already exists that's good enough," we say so. If the answer is "build a custom model," we scope it like any other software engagement: written requirements, milestones, acceptance criteria.

Capabilities · 6 areas
  • Custom ML models for narrow, well-bounded problems (classification, extraction, ranking)
  • Document intake automation — OCR + structured extraction + human-in-the-loop review
  • Natural language search over your own corpus (without sending it to a third party)
  • Predictive analytics with auditable feature engineering, not opaque black boxes
  • AI strategy review — which of the 47 vendor pitches you've heard are actually worth a pilot
  • Privacy-preserving deployment patterns (on-prem inference, federated approaches, content-free pipelines)
Who we work with

Organizations with a specific high-volume manual workflow they suspect could be partially automated, or a strategy team that needs a reality check on a pending vendor decision.

Sample engagement

A small-claims litigation practice was spending 6 hours per case extracting deadlines from court filings. We built a document-intake pipeline that flags every deadline mentioned in incoming PDFs, attorney reviews and confirms in 5 minutes per case. Throughput up 4x.

Service · 05

Industrial Automation

Control and monitoring for equipment that has to keep running, with the production network properly isolated from the corporate one. Your control plane does not inherit the office's threat model.

Open service detail

Industrial environments have safety, regulatory, and uptime requirements that consumer-IT vendors don't take seriously. We design with those constraints first: air-gapped where it matters, segmented where it doesn't, and documented at a level that survives the operator turnover that eventually happens.

Capabilities · 6 areas
  • Robotic process automation (RPA) for back-office workflows that crossed the line from "manual" to "a person's full-time job"
  • PLC programming + SCADA integration with proper version control and rollback
  • OT/IT segmentation — production network properly isolated from the corporate domain
  • Predictive-maintenance instrumentation: sensors, time-series data, alert routing
  • IoT integration with vendor-locked-down devices, where the only sane path is custom
  • Workflow optimization audits — find the part of the process that's costing 4x what it should
Who we work with

Manufacturers, logistics operators, lab facilities, and field-service organizations whose ops floor still runs on a 12-year-old WindowsCE box that nobody wants to touch.

Sample engagement

A 40-person specialty manufacturer was losing ~3 hours/day to a manual inventory reconciliation between the floor and ERP. We built a barcode-scan pipeline with offline tolerance + nightly reconciliation. Reconciliation now takes 15 minutes; gap-closing time fell from days to hours.

Service · 06

Software Development

Custom software for anything you can describe. If a workflow is yours, a tool is yours, a system is yours, we build it the way it should be built — typed, tested, documented, deployable, and structured so the next engineer (yours or ours) can pick it up without us.

Open service detail

We treat every engagement as if you'll one day hire your own team to take it over. The deliverable is documented code, not a black box. Tests are real (not vanity); the deployment story is one command, not a 9-page wiki page. "Custom" means custom — we don't have a 200-template SaaS framework you have to fit into. We have an opinionated stack and we apply it to whatever the problem actually is.

Capabilities · 8 areas
  • Anything custom — name a workflow, name a tool, name a system. Civic / governance tooling (e.g., Sacred.Vote), case management, intake automation, internal admin, public-facing apps
  • Web applications, primarily in Rust + TypeScript stacks for type-safe correctness
  • Mobile apps for the workflows that need them — never as a checkbox
  • API design + integration with the systems you already pay for (M365, Salesforce, Stripe, Plaid, etc.)
  • Legacy modernization with a documented migration path, not a forklift rewrite
  • Database design that survives 10x growth without an emergency consulting engagement
  • Self-hostable architectures — your software runs on your infrastructure if you want it to
  • Open-source-by-default where it serves you, with a clear license posture
Who we work with

Organizations with a workflow that's outgrown the off-the-shelf tools, a regulated environment where an off-the-shelf SaaS would create unacceptable data-handling exposure, or a one-of-a-kind requirement (Sacred.Vote-class civic infrastructure, niche compliance pipelines, novel research instrumentation) that no vendor sells.

Sample engagement

A nonprofit running case-management on a Google Sheets + email workflow needed real software but couldn't afford SaaS pricing tiers. We built a self-hosted case-management app on top of their existing infrastructure, documented for in-house handoff. Annual cost: $0 SaaS, ~3hr/mo maintenance.

Service · 07

Hardware Solutions

Procurement at pass-through pricing, standardized device images, and an asset register that knows who has what. Hardware is where small-organization IT quietly loses money, usually on a refresh cycle nobody owns.

Open service detail

Hardware is where small-organization IT often hemorrhages money: refresh cycles nobody owns, BYOD chaos that breaks compliance, and surprise vendor markups on "managed" purchases. We standardize the fleet, write the lifecycle policy, and source competitively.

Capabilities · 6 areas
  • Procurement at pass-through pricing — no license-arbitrage markup
  • Standardized device images (laptops, workstations, mobile) with proper MDM
  • Asset management: who has what, when it was bought, when it depreciates out
  • Lifecycle replacement planning — predictable budget, no surprises
  • Secure decommissioning + data destruction with documented chain of custody
  • Hardware repair coordination so a broken laptop is a 2-day inconvenience, not a 2-week one
Who we work with

Organizations whose laptop fleet is whatever the staff bought on Best Buy + a few legacy desktops nobody remembers buying. Anyone preparing for an audit that asks "what hardware are you running?"

Sample engagement

A 25-person practice had 19 different laptop configurations, no asset register, and three machines running unsupported OS versions. We standardized on two refresh tiers, wrote a 3-year refresh budget, sourced competitively (saved 18% over their previous vendor), and inventoried everything that walked through the door.

Service · 08

Network Architecture

Network architecture that stays up and stays fast, without enterprise-tier complexity. We design connectivity that scales with you and stays operable by your eventual in-house IT person.

Open service detail

Most small-organization networks accumulate complexity over years until nobody understands them anymore. We start with a documented current-state diagram, then design a target state that's simpler, faster, and properly segmented. No mesh-of-tunnels architectures that nobody can debug at 2am.

Capabilities · 7 areas
  • Network design + documentation (the diagram + the rationale behind every decision)
  • VPN solutions: WireGuard for new builds, OpenVPN where legacy compatibility demands it
  • Wi-Fi architecture: coverage, capacity, segmentation (guest / staff / IoT properly separated)
  • Connectivity audits — find the dual-uplink that became a single point of failure when one circuit was canceled
  • Firewall ruleset cleanup with documented rationale for every rule that survives
  • Tor + onion-service architecture for organizations whose threat model warrants it
  • Zero-trust patterns sized to small teams, not Fortune 500 implementations
Who we work with

Organizations whose network is "whatever the previous IT person set up" plus a few hardware swaps over the years. Anyone preparing to expand to a second location or a hybrid-remote workforce.

Sample engagement

A regional firm with three offices was running a hub-and-spoke VPN that fell over weekly. We replaced it with a mesh WireGuard setup, segmented per-office and per-role, documented the topology + every firewall rule. Outages dropped from weekly to none in the first 90 days.

Method

How the security work is actually done.

Two quotes for a penetration test can differ by a factor of five and describe the same words. One is a person working through your application; the other is a scan with a cover page. The difference is the method, so here is ours in enough detail that you can compare it against anyone else's.

Standards the work runs against

PTES
Sets the engagement phases — pre-engagement scoping, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post-exploitation, reporting. It is why the scope conversation happens before the invoice, not after.
NIST SP 800-115
The technical assessment method: plan, discover, attack, report. It governs how evidence is captured and how a finding is substantiated, which is what makes a report defensible to an auditor who was not in the room.
OWASP ASVS
Web application verification requirements. We test against a stated level and tell you which one, so "we tested the application" becomes a list of specific requirements that passed or failed.
MITRE ATT&CK
Findings are mapped to technique IDs. Your detection engineering then has something concrete to build against, instead of a severity rating and a paragraph.
CIS Benchmarks
Configuration baselines for the platforms in scope. Useful because most of what we find in small environments is a default nobody changed, not an exotic vulnerability.

What a scanner cannot find

  • Business logic — a checkout that lets you apply the discount after the total is computed. Every request is individually valid, so nothing flags.
  • Chained privilege escalation — three findings rated low that combine into domain admin. A scanner grades findings one at a time and never tries the combination.
  • Authorization gaps — the endpoint works exactly as built; it just never checks whether this user should be allowed to call it for that record.
  • Multi-step workflow abuse — approving your own request by completing the steps out of order.

What lands on your desk

  • An executive summary in plain English, written for the partner or practice manager who has to decide what to fund.
  • Technical findings with reproduction steps and evidence, so your engineers can confirm each one without asking us what we meant.
  • Remediation guidance specific to your stack, not a link to a vendor advisory.
  • Anything critical reaches you the day we find it. We do not sit on a live issue to preserve the drama of the final report.
  • A retest of high and critical findings within 30 days, included in the price rather than sold back to you.

You can read the report this produces before buying one. Scope, price and the retest window are agreed in writing before any testing starts — see how we work.

How we approach every engagement

Different shapes, same posture.

Whether the engagement is a $1,500 discovery, a $9,500/mo retainer, or a $60,000 fixed-scope project, the operating posture is identical: written proposals, scope-limited access, audit-ready documentation, and a real handoff path.

We aim for engagements that produce documentation a competent successor can use to take over. The next vendor — yours or ours — should be able to read what we built, understand why, and run it without us. That's what "compose, don't compromise" means at the engagement level.

Read more in how we work or check our pricing posture.

Not sure where to start?

The intake conversation is free, the NDA is mutual, and we'll tell you if we're not the right fit. Tell us what's on your plate — even if you're not sure whether it's an IT problem yet.

Or write to team@plausiden.com · 978-351-6495