StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Home
  2. Companies
  3. Blackbaud
Blackbaud

Blackbaud

charlestonblackbaud.com

Blackbaud is a supplier of software and services for non-profit organizations.

48tools
1decisions
0followers
OverviewTech Stack48Dev Feed

Tech Stack

View all 48
Stack by Layer
Application & Data29
Utilities7
DevOps1
Business Tools11
Application & Data
29 tools (60%)
Utilities
7 tools (15%)
DevOps
1 tools (2%)
Business Tools
11 tools (23%)

Application & Data

29
BootstrapAmazon S3FastlyDynNGINXJavaEmber.jsWordPressAnimate.css ModernizrBackbone.jsLodashMicrosoft AzureAmazon EC2AngularJSApache HTTP ServerPHPHandlebars.jsSlickASP.NETApache TomcatGoogle Code PrettifySitefinityAmazon CloudFrontMicrosoft IISMoment.jsGoogle Cloud Platform.NETAmazon Web Services (AWS)

Utilities

7
Google AnalyticsStripeMixpanelOpenSSLGoogle Tag ManagerMandrillKISSmetrics

DevOps

1
New Relic

Business Tools

11
jQueryFont AwesomeReactAdRollGoogle FontsSelect2YUI LibraryPrototypeAddThisjQuery UIMarketo

Latest from Engineering

View all
Brandon Stirnaman
Brandon Stirnaman

Architect at Blackbaud

Nov 30, 2018

Needs advice

I chose .NET Core because it finally let me work natively on my macOS and Linux machines but collaborate with coworkers using Windows. Devs use the devices that they feel most capable with.

Having services that can run without changes on Linux let us migrate to containerized deployments on Kubernetes without much effort. The performance we've gotten from small ASP.NET Core services running on Alpine images has been great.

While the versioning of SDK and libraries/meta packages/etc has been kind of nuts.. We also keep getting new features that are really valuable and easy to package into our services.

Just rolling out v3 of the WebJobs SDK which brought simpler DI, filters and more to our Async backend workers. Also preparing to run v2 of Functions in our Azure Kubernetes cluster with virtual-kubelet.

In the last year, the community has finally started heavily moving towards NETStandard 2.0 which has eliminated some of our last points of frustration -- not finding compatible clients/libraries/tools that we could use from .NET Core apps (and, funny enough our older .NET Framework apps too!).

We're all in on .NET Core now.

5.09k views5.09k
Comments