We’re excited to roll out a new integration - this time with LaunchDarkly.
LaunchDarkly is a feature management and experimentation platform that enables high-velocity teams to release, monitor, and optimize software in production. By separating code deployments from feature releases, LaunchDarkly enables engineering teams to deploy faster, reduce risk, and iterate continuously.
Port, on the other hand, is a platform for open internal developer portals. Port consolidates everything developers need to know and execute to deliver software more productively and to comply with organizational standards.
What does this integration mean for you?
Managing feature flags has become a common practice for teams who want to control the complexity of rollouts.
LaunchDarkly already gives users a lot of context about where and how feature flags are implemented. The Port + LaunchDarkly integration takes things a step further by providing even more insights about how flags connect to various environments and services.
Through this integration - that adds LaunchDarkly data into the internal developer portal, users will be able to:
- Understand exactly where and how feature flags are implemented across different environments.
- Gain a comprehensive overview of all feature flags used by any given microservice.
- See all the details about feature flags including configurations, available values, and default values.
- Gain insights into the specific settings of feature flags, attributes, and associated segments.
But it's more than just visibility. Port’s software catalog brings a new layer of context. Imagine this: an on-call engineer is paged and they’re suspecting that a specific feature might cause the issue. They can use a self service action to toggle off a feature flag while having all the relevant context about the incident right in the portal.
Port also enables the creation of rules that can automatically toggle feature flags based on catalog data. For example you can automatically activate a feature flag to release a feature after all the tests have successfully passed.
In addition you can easily require manual approval (from a manager for example) before toggling on or off a feature flag through Port adding another layer of control.
The Benefits of Port and LaunchDarkly Together
- Better context: Understand the scope and details of available feature flags.
- Informed usage insights: See how feature flags fit into the broader picture of your software environment.
- Streamlined management: Create, modify, and delete feature flags without jumping between tools.
- Increased safety and control: Manual approvals for changing feature flags mean you've got an additional safety net for releasing your features.
Check out Port's pre-populated demo and see what it's all about.
No email required
Contact sales for a technical product walkthrough
Open a free Port account. No credit card required
Watch Port live coding videos - setting up an internal developer portal & platform
Check out Port's pre-populated demo and see what it's all about.
(no email required)
Contact sales for a technical product walkthrough
Open a free Port account. No credit card required
Watch Port live coding videos - setting up an internal developer portal & platform
Book a demo right now to check out Port's developer portal yourself
Apply to join the Beta for Port's new Backstage plugin
It's a Trap - Jenkins as Self service UI
Further reading:
Example JSON block
Order Domain
Cart System
Products System
Cart Resource
Cart API
Core Kafka Library
Core Payment Library
Cart Service JSON
Products Service JSON
Component Blueprint
Resource Blueprint
API Blueprint
Domain Blueprint
System Blueprint
Microservices SDLC
Scaffold a new microservice
Deploy (canary or blue-green)
Feature flagging
Revert
Lock deployments
Add Secret
Force merge pull request (skip tests on crises)
Add environment variable to service
Add IaC to the service
Upgrade package version
Development environments
Spin up a developer environment for 5 days
ETL mock data to environment
Invite developer to the environment
Extend TTL by 3 days
Cloud resources
Provision a cloud resource
Modify a cloud resource
Get permissions to access cloud resource
SRE actions
Update pod count
Update auto-scaling group
Execute incident response runbook automation
Data Engineering
Add / Remove / Update Column to table
Run Airflow DAG
Duplicate table
Backoffice
Change customer configuration
Update customer software version
Upgrade - Downgrade plan tier
Create - Delete customer
Machine learning actions
Train model
Pre-process dataset
Deploy
A/B testing traffic route
Revert
Spin up remote Jupyter notebook
Engineering tools
Observability
Tasks management
CI/CD
On-Call management
Troubleshooting tools
DevSecOps
Runbooks
Infrastructure
Cloud Resources
K8S
Containers & Serverless
IaC
Databases
Environments
Regions
Software and more
Microservices
Docker Images
Docs
APIs
3rd parties
Runbooks
Cron jobs