Skip to content

Commit

Permalink
Fix Licensing Page (#5906)
Browse files Browse the repository at this point in the history
  • Loading branch information
sharadregoti authored Jan 21, 2025
1 parent bf144af commit 49ec851
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 67 deletions.
2 changes: 1 addition & 1 deletion tyk-docs/content/product-stack/tyk-charts/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,4 +21,4 @@ Tyk is working to provide a new set of helm charts, and will progressively roll
| [tyk-data-plane]({{<ref "product-stack/tyk-charts/tyk-data-plane-chart">}}) | Deploys Tyk data plane including Tyk Gateway and Pump. Data planes are managed by Tyk Dashboard and MDCB in control plane. |
| [tyk-oss]({{<ref "product-stack/tyk-charts/tyk-oss-chart">}}) | Deploys Open source Tyk Gateway and Pump |

Learn more about [Tyk Licensing and Deployment models]({{<ref "tyk-self-managed#understand-licensing-and-deployment-models">}}).
Learn more about [Tyk Licensing and Deployment models]({{<ref "tyk-self-managed#tyk-self-managed-licensepricing">}}).
2 changes: 1 addition & 1 deletion tyk-docs/content/shared/self-managed-licensing-include.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

Tyk Self-Managed is the easiest way to install Tyk Full Lifecycle API Management solution in your infrastructure. There is no calling home, and there are no usage limits. You have full control.

See [licensing and deployment models]({{< ref "tyk-self-managed#understand-licensing-and-deployment-models" >}}) to learn about the different deployment options for Self-Managed.
See [licensing and deployment models]({{< ref "tyk-self-managed#tyk-self-managed-licensepricing" >}}) to learn about the different deployment options for Self-Managed.

Register here to get a 14-day temporary licenses for the Tyk Dashboard & Developer Portal:

Expand Down
66 changes: 2 additions & 64 deletions tyk-docs/content/tyk-self-managed.md
Original file line number Diff line number Diff line change
Expand Up @@ -130,62 +130,9 @@ The full Tyk Self-Managed system consists of:

{{< img src="/img/diagrams/diagram_[email protected]" alt="Tyk Self-Managed Archtecture" >}}

### Understand Licensing and Deployment Models
### Tyk Self Managed License/Pricing

Tyk Self-Managed is the easiest way to install Tyk Full Lifecycle API Management solution in your infrastructure. There is no calling home, and there are no usage limits. You have full control.

When selecting a Tyk Self-managed license [(see the pricing page to compare the licenses)](https://tyk.io/price-comparison), you can choose between three deployment models: [Launch]({{< ref "#understand-licensing-and-deployment-models" >}}), [Flex]({{< ref "#understand-licensing-and-deployment-models" >}}) and [Global Multi-team]({{< ref "#understand-licensing-and-deployment-models" >}}). Read below to learn which model fits best for your scenario.

Are you still figuring out your requirements for your deployment around performance, resilience, availability, latency, or multi-region deployment? Look at our [API management architectural and deployment patterns 101](https://tyk.io/blog/res-api-management-architectural-and-deployment-patterns-101/) post to learn more.

#### Questions to Ask Yourself to Select your Deployment Model

1. **How many environments do you manage?**

An environment is a single grouping of a control plane and multiple gateways, representing your development lifecycle. For example, staging and production would be 2 environments.

If you have teams working on two different projects, deployed in different environments, you might have 4 different environments (staging and prod for project number 1, staging and prod for project number 2). Or, you can leverage multi-tenancy with RBAC to onboard multiple teams onto the same environment to be more cost effective. You can read more about that scenario in the blog post [How to manage multiple teams with Tyk Self-Managed](https://tyk.io/blog/easy-api-management-with-tyk-self-managed/).

You get extra developer licenses (a single control plane with 1 connected gateway for local testing on a developer's workstation) for development and testing on local computers.

2. **How many gateways do you need per environment?**

We recommend a minimum of 2 gateways per environment for redundancy & fail over. Rolling updates or blue green deployment might require additional gateways to ensure high availability during deployments.

You might also need more depending on your average load or to handle seasonal peak traffic. See [Planning for Production]({{< ref "#planning-for-production" >}}) to learn more.

3. **Are you deploying your software stack in multiple regions or datacenter?**

Do you need support for centrally managing your APIs while deploying edge gateways into multiple regions or datacenter? Do you want to ensure [data sovereignty](https://tyk.io/blog/strategies-for-dealing-with-data-sovereignty-at-scale/) in each of the regions you are deploying your APIs?

#### Launch - perfect to get started

✅ For single teams just getting started

{{< img src="/img/diagrams/tyk-selfmanaged-launch.png" alt="Tyk Self-managed Launch">}}

#### Flex - for multiple teams within a single data center or cloud

✅ For multiple teams that require high availability and horizontal scaling <br/>
✅ For Kubernetes-based deployment within one cluster / region

{{< img src="/img/diagrams/tyk-selfmanaged-flex.png" alt="Tyk Self-managed Flex">}}

#### Global Multi-team - for the largest global enterprises at scale

✅ For managing your APIs centrally while deploying edge gateways in independent clusters / regions <br />
✅ For the highest availability across data centers <br />
✅ For Kubernetes-based deployment in multiple cluster / multiple regions <br />
✅ For larger organizations [with multiple teams]({{< ref "tyk-multi-data-centre.md" >}}) and [data sovereignty](https://tyk.io/blog/strategies-for-dealing-with-data-sovereignty-at-scale/) requirements <br />

The license starts with 3 environments and 2 regions, can be extended to more environments and regions as needed.

{{< img src="/img/diagrams/tyk-selfmanaged-multiteam.png" alt="Tyk Self-managed Global Multi-team">}}


#### Don't see what you need?

[Contact us](https://tyk.io/contact/) to discuss custom or enterprise deployments.
Refer the [pricing page](https://tyk.io/pricing/)

### Tyk Dependencies and Database Support

Expand Down Expand Up @@ -242,15 +189,6 @@ Please consult with respective init system documentation for more details on how

{{< /note >}}



#### Licensing

Read more about licensing [here]({{< ref "#understand-licensing-and-deployment-models" >}}).




## Getting Started with Tyk Self-Managed

Tyk Self-Managed consists of multiple components, as described above. While the OSS Gateway and Pump are available without a license, the remaining components require one. To experience the full capabilities of our Full Lifecycle API Management solution within your own infrastructure, please obtain a license by contacting our support team.
Expand Down
2 changes: 1 addition & 1 deletion tyk-docs/data/alias.json
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@
"tyk-on-premises/installation/on-aws": "#install-on-aws-marketplace",
"tyk-on-premises/installation/on-heroku": "#install-on-heroku",
"tyk-on-premises/kubernetes": "#install-on-kubernetes",
"tyk-on-premises/licensing": "#understand-licensing-and-deployment-models",
"tyk-on-premises/licensing": "#tyk-self-managed-licensepricing",
"tyk-on-premises/microsoft-azure": "#install-on-microsoft-azure",
"tyk-on-premises/on-aws/ec2": "#install-on-aws-marketplace",
"tyk-on-premises/redhat-rhel-centos": "#install-database",
Expand Down

0 comments on commit 49ec851

Please sign in to comment.