> Full Neon documentation index: https://neon.com/docs/llms.txt

# Unlimited org members on the Free plan, Neon Auth updates, and more

## Unlimited Neon org members on the Free plan

You can now add **unlimited members** to each organization on the Free plan. Collaborate with teammates, invite others to your org, or keep separate workspaces for personal projects, side projects, and collaborations.

![Unlimited members on the Free plan](https://neon.com/docs/changelog/unlimited_members.png)

**Info: What are orgs and members?** An **organization** is a workspace that owns Neon projects and where you manage projects and collaborate. **Members** are people you invite to your organization. [Learn more](https://neon.com/docs/manage/orgs-manage).

With unlimited members, listing them efficiently matters. The [API for listing organization members](https://api-docs.neon.tech/reference/getorganizationmembers) now supports **pagination** and **sorting**, and the Console members page supports sorting and pagination. Member objects also include an optional **`has_mfa`** field, and the Console shows a 2FA indicator, following the recent introduction of [two-factor authentication (2FA)](https://neon.com/docs/manage/accounts#two-factor-authentication).

<details>

<summary>**Organizations API example**</summary>

```bash
# First page
curl -X GET \
  'https://console.neon.tech/api/v2/organizations/{org_id}/members?limit=20&sort_by=joined_at&sort_order=desc' \
  -H 'Authorization: Bearer $NEON_API_KEY'

# Next page (use cursor from response.pagination.next)
curl -X GET \
  'https://console.neon.tech/api/v2/organizations/{org_id}/members?limit=20&cursor=...' \
  -H 'Authorization: Bearer $NEON_API_KEY'
```

Response includes `pagination.next` for the next page and, per member, a `user` object that may include `has_mfa`:

```json
"user": { "email": "user@example.com", "has_mfa": true }
```

</details>

## Neon Auth

We're introducing two new Neon Auth features this week.

**Organization settings.** You can now configure **Organizations** for Neon Auth from the Neon Console. Go to **Auth** > **Configuration** > **Organizations** (per branch) to enable or disable the plugin, set the maximum organization memberships per user and the maximum members per organization, choose the creator role (owner or admin) for new organizations, and control whether invitation emails are sent. These settings support multi-tenant apps where users create and join organizations. See [Organization](https://neon.com/docs/auth/guides/plugins/organization) in the Neon Auth docs.

![Auth Configuration > Organizations in the Neon Console](https://neon.com/docs/changelog/auth_organizations_ui.png)

**Webhooks.** Introducing **Neon Auth webhooks**. Configure webhooks to receive HTTP POST requests when authentication events occur (OTP delivery, magic link delivery, user creation). Use them to replace built-in email delivery with your own channels (SMS, custom email, WhatsApp), validate signups before they complete, or sync new users to CRMs and analytics. The guide covers event types, API configuration, payload structure, signature verification, expected responses, retry behavior, and testing. See [Webhooks](https://neon.com/docs/auth/guides/webhooks).

## New NAT gateway IPs and VPC endpoint services in US East (N. Virginia)

We've expanded infrastructure capacity in the AWS US East (N. Virginia) region (`us-east-1`) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

**Tip: Update your IP allowlists** If you have IP allowlists on external systems that Neon connects to, **update those allowlists to include the new NAT gateway addresses**. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

If you use Private Networking in `us-east-1`, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the [Regions documentation](https://neon.com/docs/introduction/regions#aws-nat-gateway-ip-addresses) for the complete list of NAT gateway IPs and the [Private Networking guide](https://neon.com/docs/guides/neon-private-networking) for VPC endpoint service addresses by region.

## Stay on top of network transfer costs

![Network transfer monitoring](https://neon.com/docs/changelog/network_transfer.png)

**Network transfer** (egress) is data sent from your Neon databases to clients. It's one of the usage metrics that affects your bill on paid plans, and many teams only notice it when it shows up as a line item.

We've added two things to help. First, a **guide** that explains what network transfer is, what typically drives it (queries, pg_dump, logical replication, log export), how to monitor it in the Console and via the Consumption API, and how to manage or reduce usage. See [Reduce network transfer costs](https://neon.com/docs/introduction/network-transfer).

Second, an **agent skill** that guides your AI assistant through diagnosing and fixing application-side query patterns that cause excessive egress. The skill walks through analyzing your codebase for anti-patterns (such as `SELECT *`, missing pagination, high-frequency queries on static data, and application-side aggregation), applying fixes, and verifying with tests. To add it:

```bash
npx skills add neondatabase/agent-skills -s neon-postgres-egress-optimizer
```