---
title: "Serverless"
description: "Learn more about serverless support, which is available out of the box."
url: https://docs.sentry.io/platforms/go/guides/grpc/usage/serverless/
---

# Serverless | Sentry for gRPC

## [Source Context](https://docs.sentry.io/platforms/go/guides/grpc/usage/serverless.md#source-context)

`sentry-go` works with serverless runtimes out of the box.

If you want source lines in stack traces, see [Source Context](https://docs.sentry.io/platforms/go/source-context.md).

This guidance is the same for serverless and non-serverless Go deployments.

### [Events Delivery](https://docs.sentry.io/platforms/go/guides/grpc/usage/serverless.md#events-delivery)

Most (if not all) serverless solutions won't wait for network responses before closing the process. Because of that, we need to make sure that the event is delivered to Sentry's servers.

It can be achieved twofold, using the [`sentry.Flush` method](https://docs.sentry.io/platforms/go/guides/grpc/configuration/draining.md) or by swapping the transport to [`HTTPSyncTransport`](https://docs.sentry.io/platforms/go/guides/grpc/configuration/transports.md#httpsynctransport).