What are the opening hours?

Monday 9am - 5pm Tuesday 9am - 5pm Wednesday 9am - 5pm Thursday 9am - 5pm Friday 9am - 5pm

NextLink Labs

Name: NextLink Labs
Address: 2545 Railroad Street Suite 100, Pittsburgh, PA, 15222, US
Telephone: +14122583252

At NextLink Labs we are focused on delivering strategy and executions with the goal to optimize business outcomes. Contact us to learn more!

NextLink Labs helps companies achieve lasting success with best-in-class technology! We utilize Cybersecurity Strategies, DevOps Services, and Custom Software Solutions to meet your business's goals.

05/06/2026

Tomorrow we're joining Catalyst Connection for a webinar on AI in manufacturing engineering — and I want to be honest about why we agreed to do it.

Most AI conversations in manufacturing right now are either too abstract to act on, or they're a product demo in disguise.

What Saunders, Burmaster, and Chellappan are going to talk about tomorrow is different — what engineering teams inside manufacturing companies can actually implement today, without overhauling their stack or betting on tools that aren't ready.

If you're a CTO, engineering manager, platform engineer, or controls engineer trying to figure out where AI genuinely fits into your practice — this is the hour worth clearing on your calendar.

📅 Tomorrow — Thursday, May 7
🕛 11:00 AM – 12:00 PM ET
💻 Free. Online.

Link in the comments — seats are still open.

05/04/2026

We're joining Catalyst Connection this Thursday for a webinar we've been wanting to run for a while.

AI Without the Hype: What Engineering Teams in Manufacturing Can Actually Do Today.

Not a demo. Not a vendor pitch. A real conversation about where AI fits into engineering practice inside manufacturing companies — and where it doesn't.

If your team builds and maintains the software that powers your products, machines, or operational systems, this is for you.

Saunders, Burmaster, and Chellappan from NextLink Labs will be leading the session — 20+ years of combined experience helping technology leaders cut through the noise and find what actually works.

📅 Thursday, May 7
🕛 12:00 PM – 1:00 PM ET
💻 Free. Online.

Registration link in the comments.

04/29/2026

Two problems that eat engineering time every week.

Writing GitLab pipelines from scratch.
Most CI files start from a half-broken template nobody fully trusts — no scanning, no caching, no parallel stages. Rewriting them is fine work, but it's slow and the mistakes don't show up until the first failed run at 2pm on a Tuesday.

Alex Podobnik has been using Claude Code for internal GitLab pipelines and wrote up exactly what that workflow looks like — rootless BuildKit, Trivy scanning with a hard fail on HIGH and CRITICAL, proper layer caching, and a staging tag so vulnerable images never touch the registry. Where Claude Code earns its keep, and where it doesn't.

Importing existing infrastructure into Terraform.
You open the AWS console, find 15 EC2 instances, a dozen S3 buckets, and a VPC with security groups nobody fully understands — all created by hand, none of it in code. The old way: pull the details, write the HCL, run plan, read the diff, fix it, repeat. 15 minutes per resource. 50 resources. Do the math.

With Claude Code running the agentic loop — pulling from AWS CLI, writing HCL, running plan, reading the diff, fixing it — 25 S3 buckets takes 20–30 minutes unattended.

Both pieces just dropped in the NextLink newsletter. Written by engineers, for engineers.

Links in the comments.

04/27/2026

Every infrastructure engagement has the same moment.

You open the AWS console and find 15 EC2 instances, a dozen S3 buckets, a VPC with security groups nobody fully understands — all created by hand, none of it in Terraform.

Getting it under Terraform management is one of the most tedious jobs in infrastructure work. Not because it's hard. Because it's slow.

The old way:
→ Pull the resource details from AWS
→ Figure out the right Terraform resource type
→ Write the HCL by hand
→ Run terraform plan, see a massive diff
→ Tweak, re-plan, repeat

For one resource: 15 minutes.
For 50 resources: a full day.

Claude Code changes this entirely. You hand it the job, it runs the AWS CLI itself, writes the HCL, runs the plan, reads the diff, fixes it, and loops until the plan is clean — unattended.

25 S3 buckets: 20–30 minutes of Claude Code working while you do something else. By hand: most of a day.

Podobnik wrote up exactly how we structure this — the CLAUDE.md setup, the agentic loop, and how to scope bulk imports without losing control of what gets touched.

Link in the comments.

04/22/2026

Two things shipping engineers deal with every week:

Your AI coding assistant doesn't actually know your database.
Claude Code can read your code, run your tests, and refactor entire modules — but ask it "how many active users do we have?" and it's guessing. It's reading your models, inferring your schema, and suggesting a query you still have to run yourself.

The fix is a lightweight MCP server — 100 lines of Node.js, 60 lines of Ruby — that gives Claude Code safe, read-only SQL access to your Rails app. Then it can just answer the question directly.

Your AWS accounts are being managed by hand.
One account becomes two, two becomes five, and eventually someone is clicking through the console trying to remember which account has which guardrails. SCPs drift. Exceptions get added. Nobody documents it.

AWS Organizations + Terraform is the fix. Treat any console-based SCP change as immediate technical debt.

Both of these just landed in the NextLink newsletter — Colin Soleim on the MCP server build, Alex Podobnik on AWS Organizations. Practical and ready to implement.

Links in the comments.

04/21/2026

Your software has vulnerabilities. That's not a maybe — it's a mathematical certainty.

The average application has 20–30 open-source dependencies. Each one carries its own history of CVEs, misconfigurations, and undiscovered flaws. Multiply that across every service, library, and infrastructure component in your environment and the attack surface becomes enormous.

Traditional scanning tools catch what they know. They're pattern matchers — great at flagging known signatures, terrible at reasoning about context.

They can't tell you:
→ Is this CVE actually reachable in my application?
→ Does this IAM policy become dangerous in combination with this S3 bucket and this Lambda trigger?
→ Is this business logic flaw even on the map?

That gap between "this vulnerability exists" and "this vulnerability is exploitable in your environment" is where most real risk lives.

It's also where we've integrated Claude into our security assessment workflow.

Not to replace our security engineers. To make them faster, more thorough, and harder to fool. Claude handles the systematic review. Our engineers focus on what actually matters.

Travis Burmaster, Solution Architect at NextLink Labs, wrote up exactly how we structure this — the context engineering, the iterative depth, and what it means for how clients prioritize remediation.

Worth a read if you're responsible for a software portfolio and want to know where your real risks are — not just the ones your current tooling can see.

🔗 Full post in the comments.

04/15/2026

Two things that quietly slow down every engineering team:

Infrastructure that drifts between environments.
Production looks nothing like staging. Staging looks nothing like dev. Nobody knows when it diverged — or why.

AI tools that don't actually know your codebase.
You give Claude Code access to a 400-model Rails app. It doesn't know your soft delete patterns, your filter conventions, or your role mappings. So it guesses.

Both problems are fixable. Both fixes are boring in the best way — configuration over cleverness.

This month's newsletter covers both:

→ How to use Terraform Workspaces so drift becomes structurally impossible — one module, one pipeline, one workspace convention. The only differences between environments are the ones written down.

→ How to configure Claude Code for large Rails codebases so it's actually productive — CLAUDE.md , MCP database access, and why Ruby is, as Garry Tan put it, "LLM catnip."

Written by engineers. No fluff.

If this is the kind of content you want in your inbox every month, subscribe link is in the comments.

Address

2545 Railroad Street Suite 100
Pittsburgh, PA
15222

Opening Hours

Monday	9am - 5pm
Tuesday	9am - 5pm
Wednesday	9am - 5pm
Thursday	9am - 5pm
Friday	9am - 5pm

Telephone

+14122583252

Website

https://nextlinklabs.com/

Alerts

Be the first to know and let us send you an email when NextLink Labs posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to NextLink Labs:

Want your business to be the top-listed Computer & Electronics Service in Pittsburgh?