Skip to main content

Environments (Beta)

BETA FEATURE

This feature is currently in beta. If you wish to participate, you must first request access. A member of our team will follow up to discuss the steps to get the feature enabled.

Out of the box, Meroxa comes with a multi-tenant Common Environment with which you can deploy and manage data applications. Environments make it easy to deploy network-isolated instances of Meroxa for teams with security and compliance requirements or the need to isolate development resources. All without losing the benefits of the platform.

This overview will walk you through a high-level of the requirements, the types of environments Meroxa supports, and current limitations of the beta.

Requirements

  1. Request access to the Self-hosted Environments beta. A member of our team will follow up to discuss the steps to get the feature enabled.
  2. Sign up for a Meroxa account here.
  3. Ensure your cloud account has the capacity for Meroxa to create an environment. Each environment will create 1 VPC and 4 Elastic IPs.
  4. Install the latest Meroxa Command Line Interface (CLI). Refer to our installation guide for all available install and update methods.

Types of Environments

Common (Default)

The Common Environment is the current publicly available multi-tenant SaaS offering on our platform. This environment is fully-managed and owned by Meroxa. Security measures are in place to keep your data private, but each instance is not fully network-isolated.

Common Meroxa Environment

Self-hosted (Beta)

The Self-hosted Environment is fully network-isolated and deployed into a Meroxa-created VPC within your cloud account. It is managed and supported by the Meroxa platform remotely. You might use this environment if you have compliance and security requirements or require isolation of your development resources.

Self-Hosted Meroxa Environment

Private (Beta-limited)

The Private Environment is fully network-isolated and deployed into a Meroxa-created VPC within a Meroxa fully-managed and owned cloud account. You might use this environment if you have compliance and security requirements or require isolation of your development resources—but don't want to manage or own the account with the cloud provider. This option is currently limited to select customers. Please let us know if you have this requirement.

Limitations of the beta

During beta, there are a few limitations to be aware of:

  • A single Self-hosted Environment or Private Environment may be provisioned at a time.
  • The application framework only works with the Common Environment.
  • Amazon Web Serivces (AWS) is currently the only supported substrate in select regions.
NOTE

Are you using a cloud provider other than Amazon Web Services (AWS)? Reach out and let us know—we'd love to hear about your use case!

What's Next?

Get started with Self-hosted Environments