How to manage your self-hosted Baserow instance ID

Your instance ID connects self-hosted Baserow to premium subscriptions. Find it in Admin → Licenses (admin access required). Instance IDs can be changed for active subscriptions to support server migrations.

Quick overview

Baserow instance IDs uniquely identify your self-hosted installation for premium licensing. This system enables centralized subscription management while keeping your data on your servers.

Understanding instance IDs

Your instance ID acts as a unique identifier that links your self-hosted Baserow installation to premium subscriptions purchased through baserow.io. When you buy a premium plan, Baserow associates your license with this specific instance ID, ensuring premium features activate only on your authorized server.

This architecture separates data hosting (your servers) from subscription management (Baserow’s systems), giving you deployment control while maintaining proper licensing.

How to find your instance ID

Prerequisites

  • Instance Admin access to your Baserow installation
  • Active self-hosted Baserow deployment

Steps to locate instance ID

  1. Access admin panel: Log into your self-hosted Baserow as an Instance Admin
  2. Navigate to licenses: Go to Admin → Licenses in the interface
  3. Copy instance ID: Find and copy your unique instance ID from the licenses page

Instance ID location

Only users with Instance Admin privileges can access this information. Regular users cannot view the admin panel or retrieve instance IDs.

When to change your instance ID

Instance ID changes support several deployment scenarios:

  • Server migrations: Moving from development to production environments
  • Infrastructure upgrades: Transitioning to new server hardware or cloud providers
  • Deployment consolidation: Combining multiple instances under a single license
  • Disaster recovery: Restoring service on replacement infrastructure

How to change instance ID

You can modify the instance ID for active subscriptions through the subscription management interface at baserow.io. This process maintains license compliance and billing continuity while supporting deployment flexibility.

The change process ensures your premium features transfer seamlessly to the new instance without service interruption or additional license costs.

Instance ID vs deployment scenarios

Scenario Instance ID action License impact
Server migration Change to new instance License transfers
Development/production split Use separate IDs Requires separate licenses
Backup/disaster recovery Change to recovery instance License transfers
Load balancing setup Single ID across nodes One license covers cluster

Frequently asked questions

Can regular users access instance IDs?

No, only Instance Admins can view instance IDs through the admin panel. Regular users don’t have access to licensing information or administrative functions.

How often can I change my instance ID?

Baserow allows instance ID changes for legitimate deployment needs like migrations or infrastructure updates. The system prevents abuse while supporting normal operational requirements.

What happens if I lose my instance ID?

Instance Admins can always retrieve the current instance ID from the admin panel. If you’ve lost admin access, contact Baserow support to verify your account and assist with instance identification.

Do I need a new subscription for a new server?

Not necessarily. If you’re migrating or replacing an existing deployment, you can change the instance ID to transfer your existing license. New additional deployments require separate subscriptions.

Troubleshooting instance ID issues

Cannot access admin panel

Verify you have Instance Admin privileges. Contact your system administrator if you should have admin access but cannot see the Admin option in your interface.

Instance ID not displaying

Ensure your Baserow installation is properly configured and running the latest version.

License not activating after ID change

Allow up to 15 minutes for license changes to propagate. If premium features remain unavailable, verify the instance ID was updated correctly in your subscription settings.

Need help?