Everyone has an idea. But there’s a major difference between having an idea and being able to build it.

At New Relic, we’ve always had a soft spot for the builders. After all, many of us have built and scaled startups ourselves (like IOpipe and Pixie Labs), played a role in New Relic’s growth from the early days of monitoring Ruby web applications, or served as advisors for early stage startups.

While you might have a great product market fit, a prototype, and a pitch deck, an idea is often only as good as the infrastructure you have to scale it. With this in mind, we’ve recently launched New Relic for Startups as part of the Amazon Web Services (AWS) Activate Console to help builders build faster from day 0. 

As part of AWS Activate + New Relic for Startups, startup founders and engineering teams get exclusive discounts, free credits, and support for New Relic’s cloud-based observability platform.

If you’re an early-stage startup interested in joining AWS Activate, sign up at AWS Activate. To enroll in the program as an existing AWS Activate member, select New Relic in the console to get started monitoring, troubleshooting, and optimizing all of your AWS services.

Your ideas need uptime, and we’re here for it. Whether you’re on day 0 or day 300, here are five things all AWS Activate startup founders and engineers should do to build and scale their next big idea with New Relic.

1. Start with unlimited access to the same dev tools used by world-class engineering orgs

Every engineer should have access to best-in-class tooling right out of the gate. While all developers can build a functional app with a repo and an S3 bucket, many early-stage startups feel the pressure to compromise on their tooling choices due to implementation complexity or price.

Whether you’re building with an engineering team of 2 or 20, New Relic One gives startup teams a cohesive debug workbench with immediate analysis for errors, transactions, metrics, logs, and more. With AIOps baked in and quick access to contextual log data for root-cause analysis for any event, you can drill down into the meta details for any performance issues before they affect your user base.

2. Avoid the stress of expensive monitoring tools

Spend less money on tooling and more money on R&D, engineering talent, and good coffee. Contrary to popular belief, monitoring your apps and systems doesn’t have to be an exercise in deciphering a mix of hosts, traces, logs and metrics, and sampling data that results in blind spots. You don't have to patch together different tools and data sets for logs, infrastructure monitoring, tracing, and more.

New Relic for Startups through AWS Activate provides generous credits and discounts so you can focus on building new features while preserving your burn rate.

3. Establish DevOps and data-driven engineering practices early

In a startup, shipping and being responsible for code in production is often everyone’s problem. Building and shipping fast often means using managed services to abstract away infrastructure management. But when things go wrong, it can be a lot trickier to detangle the issue.

With distributed tracing and logs-in-context from New Relic in place from Day 0, your team can quickly isolate which service or call is causing latency, and then drill down to the log level in just a couple clicks to get the meta details so you can solve the issue.

In addition, with all of your metrics, events, logs, and traces living in one managed database with unlimited queries and dashboards, you’ll get a real-time view of how users are interacting with your product—to both influence your feature planning and critical metrics.

4. Get instant monitoring for your entire AWS environment

Whether it’s visualizing and debugging AWS Lambda invocation errors or containers on Amazon Elastic Kubernetes Service (Amazon EKS), startups can visualize nearly any AWS service within New Relic. Integrations include Amazon Elastic Compute Cloud (Amazon EC2), Amazon EKS, Amazon Elastic Container Service (Amazon ECS), Amazon Simple Storage Service (Amazon S3), AWS Lambda, Amazon DynamoDB, Amazon API Gateway—and the list goes on.

The best part? You can troubleshoot all of these AWS services alongside the rest of their distributed environment, whether it’s other third-party services and APIs or simply components hosted somewhere else.

As an example, let’s say your startup is using Amazon EKS to containerize and run a checkout service with a lot of different components. You received a Slack notification that one of your containers is running out of memory based on predefined alerts provided by New Relic:


In just two clicks, you can go from a critical, red pod in production to the meta details—and now down to the log level. You can see that there’s a stress process causing the issue, and you can fix it by modifying the code or changing your memory thresholds.

And you can do the same type of troubleshooting flow across nearly any AWS service:

5. Get started without a sales conversation

You don’t always have time to talk to a salesperson, especially when you’re trying to debug an issue. You’d rather sign up, solve your issue, and explore features on your own schedule with your own data.

With New Relic, startups can sign up directly from the AWS Activate Console, and our guided install helps you auto-instrument your AWS services starting directly from the command line.

No demo or sales conversation needed.