PageSourceSearch

https://comnatix.com/

html comnatix.com collected 2026-10-02 01:25:56 UTC 29,576 bytes, 503 lines download raw bytes

1<!DOCTYPE html>
2<html lang="en">
3<head>
4  <meta charset="UTF-8" />
5  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6  <title>Comnatix | AI automation, cloud & compliance, built for production</title>
7  <meta name="description" content="Comnatix builds production AI for the work your team does by hand. n8n orchestration, LangChain agents, AWS Well-Architected cloud, compliance audits, and specialist staffing. Based in Durham, NC." />
8  <meta name="theme-color" content="#ffffff" />
9
10  <meta property="og:type" content="website" />
11  <meta property="og:title" content="Comnatix | Put your busywork on autopilot" />
12  <meta property="og:description" content="Production AI for your operations: workflow automation, AWS cloud, compliance audits, and the engineers to run it. Traceable end to end." />
13  <meta property="og:image" content="assets/comnatix-logo.png" />
14
15  <link rel="icon" type="image/svg+xml" href="assets/favicon.svg" />
16  <link rel="apple-touch-icon" href="assets/comnatix-logo.png" />
17
18  <link rel="preconnect" href="https://fonts.googleapis.com" />
19  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
20  <link href="https://fonts.googleapis.com/css2?family=Inter+Tight:wght@400;500;600;700&family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet" />
21
22  <link rel="stylesheet" href="styles.css" />
23</head>
24<body id="top">
25
26  <!-- ===================== NAV ===================== -->
27  <header class="nav" id="nav">
28    <div class="nav__inner">
29      <a class="nav__brand" href="#top" aria-label="Comnatix home">
30        <img src="assets/comnatix-logo-dark.png" alt="Comnatix" class="nav__logo nav__logo--light" />
31        <img src="assets/comnatix-logo.png" alt="Comnatix" class="nav__logo nav__logo--dark" />
32      </a>
33      <nav class="nav__links" id="navLinks" aria-label="Primary">
34        <a href="#services">Services</a>
35        <a href="#usecases">Use cases</a>
36        <a href="#approach">Approach</a>
37        <a href="#faq">FAQ</a>
38        <a href="#contact" class="nav__cta">Start a project</a>
39      </nav>
40      <button class="nav__toggle" id="navToggle" aria-label="Open menu" aria-expanded="false">
41        <span></span><span></span>
42      </button>
43    </div>
44  </header>
45
46  <main>
47    <!-- ===================== HERO ===================== -->
48    <section class="hero" id="hero">
49      <div class="hero__aurora" aria-hidden="true"></div>
50      <div class="hero__grain" aria-hidden="true"></div>
51
52      <div class="hero__inner">
53        <p class="eyebrow hero__eyebrow">AI consulting &amp; engineering · Production AI, cloud &amp; compliance</p>
54
55        <h1 class="hero__title" aria-label="Automate the busywork. Prove every move.">
56          <span class="line">
57            <span class="w" style="--d:.20s">Automate</span>
58            <span class="w" style="--d:.30s">the</span>
59            <span class="w sheen" style="--d:.40s">busywork.</span>
60          </span>
61          <span class="line">
62            <span class="w" style="--d:.58s">Prove</span>
63            <span class="w" style="--d:.68s">every</span>
64            <span class="w" style="--d:.78s">move.</span>
65          </span>
66        </h1>
67
68        <p class="hero__lede hero__fade" style="--d:1.0s">
69          We turn the manual, repetitive work that slows your business into AI that runs on its own.
70          Built to production standards, governed by default, and traceable end to end, so the work
71          takes care of itself and every decision holds up to scrutiny.
72        </p>
73
74        <div class="hero__actions hero__fade" style="--d:1.15s">
75          <a href="#contact" class="btn btn--primary">Book a discovery call</a>
76          <a href="#approach" class="btn btn--link">See how we build</a>
77        </div>
78      </div>
79
80      <div class="hero__foot hero__fade" style="--d:1.4s">
81        <a href="#services" class="hero__scroll" aria-label="Scroll to content">Scroll</a>
82      </div>
83    </section>
84
85    <!-- ===================== TRUST / STACK STRIP ===================== -->
86    <section class="trust" aria-label="Technology we build on">
87      <p class="trust__label">Built on the tools your engineers already trust</p>
88
89      <div class="marquee">
90        <div class="marquee__row marquee__row--l">
91          <div class="marquee__group">
92            <span class="m">AWS</span><span class="m">Azure</span><span class="m">Google Cloud</span><span class="m">n8n</span><span class="m">Zapier</span><span class="m">Make</span><span class="m">LangChain</span><span class="m">LlamaIndex</span><span class="m">Amazon Bedrock</span><span class="m">Azure OpenAI</span><span class="m">Vertex AI</span><span class="m">OpenAI</span><span class="m">Anthropic</span><span class="m">Hugging Face</span><span class="m">Terraform</span><span class="m">Docker</span><span class="m">Kubernetes</span><span class="m">Lambda</span><span class="m">ECS</span><span class="m">Ansible</span>
93          </div>
94          <div class="marquee__group" aria-hidden="true">
95            <span class="m">AWS</span><span class="m">Azure</span><span class="m">Google Cloud</span><span class="m">n8n</span><span class="m">Zapier</span><span class="m">Make</span><span class="m">LangChain</span><span class="m">LlamaIndex</span><span class="m">Amazon Bedrock</span><span class="m">Azure OpenAI</span><span class="m">Vertex AI</span><span class="m">OpenAI</span><span class="m">Anthropic</span><span class="m">Hugging Face</span><span class="m">Terraform</span><span class="m">Docker</span><span class="m">Kubernetes</span><span class="m">Lambda</span><span class="m">ECS</span><span class="m">Ansible</span>
96          </div>
97        </div>
98
99        <div class="marquee__row marquee__row--r">
100          <div class="marquee__group">
101            <span class="m">Postgres</span><span class="m">pgvector</span><span class="m">Snowflake</span><span class="m">Databricks</span><span class="m">OpenSearch</span><span class="m">Pinecone</span><span class="m">Weaviate</span><span class="m">Qdrant</span><span class="m">Redis</span><span class="m">Kafka</span><span class="m">Airflow</span><span class="m">dbt</span><span class="m">GitHub Actions</span><span class="m">Grafana</span><span class="m">Datadog</span><span class="m">CloudWatch</span><span class="m">Salesforce</span><span class="m">NetSuite</span><span class="m">Slack</span><span class="m">Python</span><span class="m">FastAPI</span><span class="m">SOC&nbsp;2</span><span class="m">ISO&nbsp;27001</span>
102          </div>
103          <div class="marquee__group" aria-hidden="true">
104            <span class="m">Postgres</span><span class="m">pgvector</span><span class="m">Snowflake</span><span class="m">Databricks</span><span class="m">OpenSearch</span><span class="m">Pinecone</span><span class="m">Weaviate</span><span class="m">Qdrant</span><span class="m">Redis</span><span class="m">Kafka</span><span class="m">Airflow</span><span class="m">dbt</span><span class="m">GitHub Actions</span><span class="m">Grafana</span><span class="m">Datadog</span><span class="m">CloudWatch</span><span class="m">Salesforce</span><span class="m">NetSuite</span><span class="m">Slack</span><span class="m">Python</span><span class="m">FastAPI</span><span class="m">SOC&nbsp;2</span><span class="m">ISO&nbsp;27001</span>
105          </div>
106        </div>
107      </div>
108    </section>
109
110    <!-- ===================== SERVICES ===================== -->
111    <section class="section" id="services">
112      <div class="section__head">
113        <p class="eyebrow">What we do</p>
114        <h2 class="section__title">Automate, govern, migrate, and staff. One team.</h2>
115        <p class="section__sub">Most firms sell you one of these and hand off the rest. We run all five, so the automation we build is already audited, already cloud-ready, and already staffed to keep running.</p>
116      </div>
117
118      <div class="grid grid--svc">
119        <article class="svc">
120          <span class="svc__icon" aria-hidden="true">
121            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"><circle cx="5" cy="6" r="2"/><circle cx="5" cy="18" r="2"/><circle cx="19" cy="12" r="2"/><path d="M7 6h6a3 3 0 0 1 3 3v1M7 18h6a3 3 0 0 0 3-3v-1"/></svg>
122          </span>
123          <h3 class="svc__title">AI Workflow Automation</h3>
124          <p class="svc__body">We map the work people do by hand and rebuild it as event-driven pipelines in n8n, with LangChain agents on the judgment calls. Intake, triage, reconciliation, reporting. Humans approve, the system does the rest.</p>
125          <ul class="svc__list">
126            <li>Process discovery and ROI modeling</li>
127            <li>n8n orchestration and custom nodes</li>
128            <li>LangChain agents, tools and RAG</li>
129            <li>Human-in-the-loop guardrails</li>
130          </ul>
131        </article>
132
133        <article class="svc">
134          <span class="svc__icon" aria-hidden="true">
135            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"><path d="M12 3l7 3v5c0 4.5-3 7.5-7 9-4-1.5-7-4.5-7-9V6l7-3z"/><path d="M9 12l2 2 4-4"/></svg>
136          </span>
137          <h3 class="svc__title">Compliance &amp; Governance Audits</h3>
138          <p class="svc__body">An independent read on how your data, models, and cloud actually behave, against the frameworks your customers ask about. You get evidence and a prioritized plan to fix what matters, not a checklist.</p>
139          <ul class="svc__list">
140            <li>SOC 2, HIPAA and ISO 27001 readiness</li>
141            <li>AI governance and model risk review</li>
142            <li>IAM, data-flow and access mapping</li>
143            <li>Remediation roadmap with owners</li>
144          </ul>
145        </article>
146
147        <article class="svc">
148          <span class="svc__icon" aria-hidden="true">
149            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"><path d="M4 7l8-4 8 4-8 4-8-4z"/><path d="M4 12l8 4 8-4M4 17l8 4 8-4"/></svg>
150          </span>
151          <h3 class="svc__title">AWS Well-Architected Reviews</h3>
152          <p class="svc__body">A structured review across all five pillars. We surface the risks hiding in your account, put a number on the reliability and cost wins, and hand you a fix list ranked by impact. Eligible workloads may qualify for AWS funding.</p>
153          <ul class="svc__list">
154            <li>Operational excellence and reliability</li>
155            <li>Security and least-privilege hardening</li>
156            <li>Cost and performance optimization</li>
157            <li>Sustainability and remediation plan</li>
158          </ul>
159        </article>
160
161        <article class="svc">
162          <span class="svc__icon" aria-hidden="true">
163            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"><path d="M7 18a4 4 0 0 1 0-8 5 5 0 0 1 9.6-1.5A3.5 3.5 0 0 1 17 18H7z"/><path d="M12 9v6M9.5 12.5L12 15l2.5-2.5"/></svg>
164          </span>
165          <h3 class="svc__title">Cloud Migrations</h3>
166          <p class="svc__body">From legacy data centers and IBM i to modern AWS, planned with a real dependency map, executed in waves, and proven with rollback at every cutover. Your team stays in control the whole way over.</p>
167          <ul class="svc__list">
168            <li>Discovery, wave planning and landing zone</li>
169            <li>Re-host, re-platform and re-architect</li>
170            <li>Zero and low-downtime cutovers</li>
171            <li>FinOps and post-migration tuning</li>
172          </ul>
173        </article>
174
175        <article class="svc svc--wide">
176          <span class="svc__icon" aria-hidden="true">
177            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.5"><circle cx="9" cy="8" r="3"/><circle cx="17" cy="9" r="2.2"/><path d="M3.5 19a5.5 5.5 0 0 1 11 0M15 19a4 4 0 0 1 5.5-3.7"/></svg>
178          </span>
179          <div class="svc--wide__main">
180            <h3 class="svc__title">Specialist Staffing &amp; Talent</h3>
181            <p class="svc__body">When you need the people, not just the plan, we place vetted AI, cloud, and compliance engineers, on contract, contract-to-hire, or direct, who ship from week one. Backed by the same teams who build for our clients.</p>
182            <a href="#contact" class="textlink" data-route="staffing">Talk to our staffing team</a>
183          </div>
184          <ul class="svc__list svc__list--cols">
185            <li>AI / ML and automation engineers</li>
186            <li>AWS and platform engineers</li>
187            <li>Security and GRC specialists</li>
188            <li>Data and migration leads</li>
189          </ul>
190        </article>
191      </div>
192    </section>
193
194    <!-- ===================== USE CASES ===================== -->
195    <section class="section section--alt" id="usecases">
196      <div class="section__head">
197        <p class="eyebrow">Use cases</p>
198        <h2 class="section__title">Where teams put us to work first.</h2>
199        <p class="section__sub">The fastest wins are the repetitive, rules-heavy work that already eats your team's week. A few of the workflows we are asked to automate most.</p>
200      </div>
201
202      <div class="grid grid--use">
203        <article class="use">
204          <span class="use__tag">Finance ops</span>
205          <h3>Invoices and AP, on their own</h3>
206          <p>Invoices and receipts arrive, get matched to purchase orders, flagged if they are off, and posted to your ERP. Clean ones go through untouched, exceptions land on a person's desk with the reason attached.</p>
207        </article>
208        <article class="use">
209          <span class="use__tag">Customer ops</span>
210          <h3>Inbound triage and drafting</h3>
211          <p>Every ticket and email gets read, classified, and routed, with a grounded draft reply ready for your team to approve and send. The queue stops being the first thing they dread on Monday.</p>
212        </article>
213        <article class="use">
214          <span class="use__tag">Document intake</span>
215          <h3>Onboarding, KYC, claims, contracts</h3>
216          <p>Document-heavy intake gets read, validated, and filed, with every extracted field linked back to the source page. No more copy-paste, and a citation for anything anyone questions.</p>
217        </article>
218        <article class="use">
219          <span class="use__tag">Compliance</span>
220          <h3>Evidence that collects itself</h3>
221          <p>Control checks and access reviews run continuously and file their own evidence. Audit season becomes a query you run, not a fire drill that swallows a quarter.</p>
222        </article>
223      </div>
224      <p class="use__foot">Not on the list? If it is repetitive, rules-driven, and slow, it is probably a fit. <a href="#contact" class="textlink">Tell us the workflow</a></p>
225    </section>
226
227    <!-- ===================== APPROACH / ARCHITECTURE ===================== -->
228    <section class="section" id="approach">
229      <div class="section__head">
230        <p class="eyebrow">How it works</p>
231        <h2 class="section__title">An automation that survives an audit.</h2>
232        <p class="section__sub">Most "AI automations" are a script and a prayer. Ours are real systems: orchestrated, observable, reversible, and governed. This is the reference architecture we deploy.</p>
233      </div>
234
235      <ol class="flow" aria-label="Reference automation architecture">
236        <li class="flow__step">
237          <span class="flow__n">01</span>
238          <h3>Events &amp; intake</h3>
239          <p>Email, forms, webhooks, S3 drops, schedules, ERP and CRM changes. Every source of work becomes a typed event.</p>
240          <div class="tags"><span>Webhooks</span><span>S3</span><span>Cron</span></div>
241        </li>
242        <li class="flow__step flow__step--key">
243          <span class="flow__n">02</span>
244          <h3><b>n8n</b> control plane</h3>
245          <p>n8n routes every event and handles retries, branching, rate limits and idempotency. The durable backbone, so a single failure never loses work.</p>
246          <div class="tags"><span>Routing</span><span>Retries</span><span>Queues</span></div>
247        </li>
248        <li class="flow__step flow__step--key">
249          <span class="flow__n">03</span>
250          <h3><b>LangChain</b> reasoning</h3>
251          <p>LangChain agents read context, call tools, and ground answers in your own data through retrieval, so the model acts on facts, not guesses.</p>
252          <div class="tags"><span>Agents</span><span>Tools</span><span>RAG</span></div>
253        </li>
254        <li class="flow__step">
255          <span class="flow__n">04</span>
256          <h3>Human-in-the-loop</h3>
257          <p>Confidence thresholds, approvals, PII redaction and policy checks. Low-confidence cases escalate to a person, and everything is logged.</p>
258          <div class="tags"><span>Approvals</span><span>PII</span><span>Policy</span></div>
259        </li>
260        <li class="flow__step">
261          <span class="flow__n">05</span>
262          <h3>Write-back &amp; observe</h3>
263          <p>Results land in your ERP, CRM, warehouse and dashboards, with full traceability from source event to final action.</p>
264          <div class="tags"><span>ERP/CRM</span><span>Warehouse</span><span>Alerts</span></div>
265        </li>
266      </ol>
267
268      <p class="callout">
269        <span class="callout__k">Why it matters</span>
270        Every run is traceable end to end. When your auditor asks who approved this, on what data, under which policy, the answer is one query away. That is the difference between a demo and a system you can put your name on.
271      </p>
272    </section>
273
274    <!-- ===================== WHY / PRINCIPLES ===================== -->
275    <section class="section section--alt" id="why">
276      <div class="section__head">
277        <p class="eyebrow">Why Comnatix</p>
278        <h2 class="section__title">Built like you will be audited. Because you will.</h2>
279        <p class="section__sub">The reasons teams keep us past the first project.</p>
280      </div>
281
282      <div class="grid grid--why">
283        <div class="why">
284          <h3>Production, not prototypes</h3>
285          <p>We do not hand over a clever demo that breaks under real load. Everything we ship is monitored, retried, and built to run unattended.</p>
286        </div>
287        <div class="why">
288          <h3>Governed by default</h3>
289          <p>Approvals, audit logs, and policy checks are in from day one, not bolted on after security asks. Compliance is part of the build, not a tax on it.</p>
290        </div>
291        <div class="why">
292          <h3>You own everything</h3>
293          <p>It runs in your cloud, on your accounts, with your data. We document it, train your team, and leave you able to run it without us.</p>
294        </div>
295        <div class="why">
296          <h3>No black boxes, no lock-in</h3>
297          <p>Open tools, readable workflows, and code you can see. If you want to take it in-house tomorrow, nothing stops you.</p>
298        </div>
299      </div>
300    </section>
301
302    <!-- ===================== STATS ===================== -->
303    <section class="stats">
304      <div class="stats__inner">
305        <div class="stat">
306          <span class="stat__num" data-count="5">5</span>
307          <span class="stat__label">core practices, one delivery team</span>
308        </div>
309        <div class="stat">
310          <span class="stat__num" data-count="5">5</span>
311          <span class="stat__label">AWS Well-Architected pillars reviewed</span>
312        </div>
313        <div class="stat">
314          <span class="stat__num" data-suffix="%" data-count="100">100</span>
315          <span class="stat__label">of runs traceable for audit</span>
316        </div>
317        <div class="stat">
318          <span class="stat__num">24/7</span>
319          <span class="stat__label">automations that do not take breaks</span>
320        </div>
321      </div>
322    </section>
323
324    <!-- ===================== ENGAGEMENT ===================== -->
325    <section class="section" id="engagement">
326      <div class="section__head">
327        <p class="eyebrow">Engagement</p>
328        <h2 class="section__title">How a Comnatix project runs.</h2>
329        <p class="section__sub">A real sequence, not a sales funnel. You always know what is next, what it costs, and what you will own at the end.</p>
330      </div>
331
332      <ol class="steps">
333        <li class="step">
334          <span class="step__n">01</span>
335          <h3>Discovery sprint</h3>
336          <p>Two weeks to map the workflow, the data, and the constraints. You leave with an architecture, an ROI model, and a fixed-scope proposal, even if you stop there.</p>
337        </li>
338        <li class="step">
339          <span class="step__n">02</span>
340          <h3>Build &amp; integrate</h3>
341          <p>We ship in increments you can see every week: orchestration, agents, and integrations wired into your real systems, in your cloud, under your control.</p>
342        </li>
343        <li class="step">
344          <span class="step__n">03</span>
345          <h3>Audit &amp; harden</h3>
346          <p>Before go-live, the same work is reviewed against your compliance frameworks and an AWS Well-Architected pass. Findings get fixed, not filed.</p>
347        </li>
348        <li class="step">
349          <span class="step__n">04</span>
350          <h3>Handover or run</h3>
351          <p>We document everything and train your team to own it, or stay on to operate and improve it. Your call. No lock-in, no black boxes.</p>
352        </li>
353      </ol>
354    </section>
355
356    <!-- ===================== FAQ ===================== -->
357    <section class="section section--alt" id="faq">
358      <div class="section__head">
359        <p class="eyebrow">FAQ</p>
360        <h2 class="section__title">The questions we get asked.</h2>
361      </div>
362
363      <div class="faq">
364        <details class="qa">
365          <summary>Is our workflow even a fit for automation?<span class="qa__i"></span></summary>
366          <p>If it is repetitive, rules-driven, and touches a few systems, almost certainly. The discovery sprint exists to prove it before you commit, with an ROI model attached. If it is not a fit, we will tell you in week two, not month six.</p>
367        </details>
368        <details class="qa">
369          <summary>How do you keep the AI from making things up?<span class="qa__i"></span></summary>
370          <p>Grounding and guardrails. Agents answer from your data through retrieval, every output carries a confidence score, and anything below threshold routes to a human. Low-stakes steps run automatically, high-stakes ones always get approval.</p>
371        </details>
372        <details class="qa">
373          <summary>What happens to our data?<span class="qa__i"></span></summary>
374          <p>It stays in your cloud and your accounts. We build inside your environment, scope access to least privilege, and redact PII before it reaches a model. You can see exactly what was sent, where, and why.</p>
375        </details>
376        <details class="qa">
377          <summary>Do we have to be on AWS already?<span class="qa__i"></span></summary>
378          <p>No. We meet you where you are, including legacy data centers and IBM i, and migrate when it makes sense. If you are already on another cloud, we work there too.</p>
379        </details>
380        <details class="qa">
381          <summary>
381How long until we see something working?<span class="qa__i"></span></summary>
382          <p>The discovery sprint is two weeks. After that you see working increments every week, in your systems, not slideware. First automations are typically live in weeks, not quarters.</p>
383        </details>
384        <details class="qa">
385          <summary>Can our team run it after you leave?<span class="qa__i"></span></summary>
386          <p>That is the goal. Open tools, documented workflows, and a handover that trains your people to own it. Keep us on to operate and improve it if you want, but you are never trapped.</p>
387        </details>
388        <details class="qa">
389          <summary>What does an engagement cost?<span class="qa__i"></span></summary>
390          <p>The discovery sprint is fixed scope and fixed price, and the proposal that follows is too, so there are no open meters. Tell us the workflow and we will size it on the first call.</p>
391        </details>
392      </div>
393    </section>
394
395    <!-- ===================== CTA BAND ===================== -->
396    <section class="cta">
397      <div class="cta__inner">
398        <h2>Find your first automation.</h2>
399        <p>Bring one workflow that eats your team's time. We will tell you, on the first call, whether it is worth automating and what it would take.</p>
400        <div class="cta__actions">
401          <a href="#contact" class="btn btn--invert">Book a discovery call</a>
402          <a href="tel:+12537853339" class="btn btn--ghostlight">(253) 785-3339</a>
403        </div>
404      </div>
405    </section>
406
407    <!-- ===================== CONTACT ===================== -->
408    <section class="section" id="contact">
409      <div class="contact">
410        <div class="contact__intro">
411          <p class="eyebrow">Start a project</p>
412          <h2 class="section__title">Tell us what is slowing you down.</h2>
413          <p class="section__sub">A short note is enough. We will come back with where automation, cloud, or audit would help first, usually within one business day.</p>
414
415          <dl class="contact__details">
416            <div><dt>Call</dt><dd><a href="tel:+12537853339">(253) 785-3339</a></dd></div>
417            <div><dt>Visit</dt><dd><a href="https://maps.google.com/?q=321+E.+Chapel+Hill+St,+Ste+301,+Durham,+NC+27701" target="_blank" rel="noopener">321 E. Chapel Hill St, Ste 301<br/>Durham, NC 27701</a></dd></div>
418            <div><dt>General</dt><dd><a href="mailto:[email protected]">[email protected]</a></dd></div>
419            <div><dt>Staffing</dt><dd><a href="mailto:[email protected]">[email protected]</a></dd></div>
420            <div><dt>Compliance</dt><dd><a href="mailto:[email protected]">[email protected]</a></dd></div>
421          </dl>
422        </div>
423
424        <form class="form" id="leadForm" action="https://api.web3forms.com/submit" method="POST" novalidate>
425          <input type="hidden" name="access_key" value="c1f8538d-669f-4a3e-97d5-8c2b03457899" />
426          <input type="hidden" name="from_name" value="Comnatix Website" />
427          <input type="hidden" name="subject" value="New enquiry from comnatix.com" />
428          <input type="checkbox" name="botcheck" class="hidden" style="display:none" tabindex="-1" autocomplete="off" />
429
430          <div class="field">
431            <label for="name">Name</label>
432            <input id="name" name="name" type="text" required placeholder="Your name" />
433          </div>
434          <div class="field">
435            <label for="email">Work email</label>
436            <input id="email" name="email" type="email" required placeholder="[email protected]" />
437          </div>
438          <div class="field">
439            <label for="company">Company</label>
440            <input id="company" name="company" type="text" placeholder="Company name" />
441          </div>
442          <div class="field">
443            <label for="topic">What do you need?</label>
444            <select id="topic" name="topic">
445              <option>AI workflow automation</option>
446              <option>Compliance &amp; governance audit</option>
447              <option>AWS Well-Architected Review</option>
448              <option>Cloud migration</option>
449              <option>Staffing &amp; talent</option>
450              <option>Not sure yet, let's talk</option>
451            </select>
452          </div>
453          <div class="field field--full">
454            <label for="message">A few details</label>
455            <textarea id="message" name="message" rows="4" required placeholder="What is the workflow, system, or problem?"></textarea>
456          </div>
457          <button type="submit" class="btn btn--primary btn--full" id="submitBtn">Send enquiry</button>
458          <p class="form__status" id="formStatus" role="status" aria-l
458ive="polite"></p>
459        </form>
460      </div>
461    </section>
462  </main>
463
464  <!-- ===================== FOOTER ===================== -->
465  <footer class="footer">
466    <div class="footer__inner">
467      <div class="footer__brand">
468        <img src="assets/comnatix-logo.png" alt="Comnatix" class="footer__logo" />
469        <p class="footer__tag">Ingenuity and creativity.</p>
470      </div>
471      <div class="footer__cols">
472        <div>
473          <span class="footer__k">Services</span>
474          <a href="#services">Workflow Automation</a>
475          <a href="#services">Compliance Audits</a>
476          <a href="#services">AWS Well-Architected</a>
477          <a href="#services">Cloud Migrations</a>
478          <a href="#services">Staffing</a>
479        </div>
480        <div>
481          <span class="footer__k">Company</span>
482          <a href="#usecases">Use cases</a>
483          <a href="#approach">Approach</a>
484          <a href="#engagement">Engagement</a>
485          <a href="#faq">FAQ</a>
486        </div>
487        <div>
488          <span class="footer__k">Reach us</span>
489          <a href="tel:+12537853339">(253) 785-3339</a>
490          <a href="mailto:[email protected]">[email protected]</a>
491          <a href="https://maps.google.com/?q=321+E.+Chapel+Hill+St,+Ste+301,+Durham,+NC+27701" target="_blank" rel="noopener">321 E. Chapel Hill St, Ste 301, Durham, NC 27701</a>
492        </div>
493      </div>
494    </div>
495    <div class="footer__bottom">
496      <span>© <span id="year">2026</span> Comnatix. All rights reserved.</span>
497      <span>Durham, North Carolina</span>
498    </div>
499  </footer>
500
501  
501<script src="script.js"></script>
501
502</body>
503</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.