iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use a service endpoint when the API belongs to a service component you deploy in Choreo. Use an API proxy when the API already exists and you have an OpenAPI description of it. The choice decides where the work starts, and endpoint visibility decides whether the Choreo API Gateway can expose a service endpoint at all.
Choose the right entry point
Choreo offers two routes to a managed API, and they begin from different places. A service endpoint is part of a component you build and deploy inside Choreo. An API proxy is a wrapper placed in front of an API that already exists, described by an OpenAPI specification or a URL that points to one.
| Question | Service endpoint (component in Choreo) | API proxy (existing OpenAPI API) |
|---|---|---|
| Starting point | A service component deployed in Choreo | An existing API with an OpenAPI specification or URL |
| Where configuration lives | Endpoint settings in the console, or in .choreo/component.yaml for supported buildpacks |
The proxy definition created from the OpenAPI input |
| How it reaches the gateway | Choreo exposes the endpoint through the Choreo API Gateway once it is deployed with Organization or Public visibility | Deployed to Development, tested, then promoted to Production |
| Visibility setting | Project, Organization, or Public; managed exposure requires Organization or Public | Not stated in the proxy tutorial |
| Protocol limits | Managed API exposure is unavailable for gRPC, UDP, and TCP endpoints | The tutorial is built around OpenAPI-described APIs; other protocols are not covered |
| Publication to the Developer Portal | Not stated in the endpoint guide | A separate publish step after deployment and validation |
If you are unsure which route applies, ask whether the code that serves the API is in a Choreo component you control. If it is, start with the endpoint. If the API is already running somewhere and you are adding management on top of it, start with a proxy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Set endpoint visibility before anything else
Visibility controls who can reach an endpoint and whether Choreo exposes it through the managed gateway. Set it before you deploy, because it determines the path the endpoint can take.
#1 Best Overall
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
The three visibility levels
- Project: the endpoint is reachable only from within the same project.
- Organization: the endpoint is restricted to the organization.
- Public: any client can access the endpoint, regardless of location or organization.
Choreo’s endpoint documentation states that managed API exposure is available only with Organization or Public visibility. A Project-visible endpoint therefore cannot be exposed through the managed gateway in this workflow.
The protocol exclusion
Managed API exposure does not apply to gRPC, UDP, or TCP endpoints, according to the same endpoint documentation. If your service exposes one of these protocols, plan for a different access pattern rather than expecting a managed API to appear after deployment.
The endpoint guide describes the behavior this way: “Once you deploy the service component, Choreo will expose the endpoint as a managed API through the Choreo API Gateway.” Source: WSO2 Choreo documentation, “Configure Endpoints.”
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Configure the endpoint
Each endpoint carries a set of attributes: protocol, port, network visibility, schema, and, for HTTP and GraphQL endpoints, a context path. Protocol-specific fields appear where the chosen protocol needs them.
Automatic detection for Ballerina and WSO2 MI
For REST endpoints built with the Ballerina and WSO2 MI buildpacks, Choreo detects endpoint details automatically. You can still review them in the console, but you usually do not need to enter them by hand.
Manual configuration for other buildpacks
For other listed buildpacks, you define endpoint details in the console or in a .choreo/component.yaml file in the component repository. When both are present, the file takes precedence over UI-defined and automatically generated settings. A field defined in the file is the value that applies, so a conflicting console edit will not change the running configuration.
Rank #3
- SonicWall TZ270W Appliance Only - No Service Subscription (02-SSC-2823) - Combines enterprise-grade firewalling with integrated 802.11ac Wave 2 Wi-Fi to deliver secure wired and wireless connectivity in one compact device for small offices and clinics.
- Blocks zero-day threats and ransomware with Capture ATP sandboxing enhanced by RTDMI, plus IPS and anti-malware scanning for layered protection.
- Eliminates the need for separate access points in smaller spaces thanks to built-in high-speed wireless that is simple to deploy and manage.
- Supports VPN, SD-WAN, and TLS 1.3 decryption to secure hybrid cloud access and remote workers while maintaining usability and performance.
- Delivers gigabit performance with up to 750,000 concurrent connections to handle growth in users, devices, and SaaS applications.
Build and test an API proxy
The official proxy tutorial, “Expose a Service as a Managed API,” walks through the following sequence. Its sample uses the OpenAPI Petstore API as an example only; any OpenAPI-described API follows the same general flow.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems- Create the API proxy from an OpenAPI specification file or from a URL that serves one.
- Deploy the proxy to the Development environment.
- Test the deployed API from the integrated OpenAPI Console, or send requests with cURL.
- Promote the proxy to the Production environment after testing passes.
- Publish the API to the Developer Portal so consumers can find it.
- Generate credentials and invoke the API.
Service endpoints
For a service component, the job is to deploy the component, confirm that the endpoint responds as expected, and then check that the managed API appears. The proxy tutorial’s exact console steps are written for proxies, so do not assume every label or screen matches the endpoint workflow for every service type. Check the console at the time you work.
Publish and check which environments are exposed
Deployment and publication are separate actions. Deploying or promoting an API does not, by itself, make it visible in the Developer Portal; you publish it as a distinct step after validation.
Rank #4
- 【Processor & OS】Firewall Mini PC with Intel J3710 CPU up to 2.64GHz, 4Cores 4threads 2MB L2 Cache, TDP 6.5w, supports AES-NI. It tested with pf-sens/opn-sense linux ubuntu and other popular open source os. ("DEL" key to enter BIOS)
- 【Interfaces】The firewall pc has 4 * Intel I226 lan ports, 2 * USB3.0 ports, 1 * RS232COM port, 2 * HD port, 1 * DC port. Equipped with VESA mount, you can install the micro pc behind the monitor to save space.
- 【Fanless Design】only 6.5W; fanless heat dissipation design, aluminum alloy shell, efficient and fast heat dissipation, which can withstand temperatures up to 60°C. support 24/7 hours working, no noise.
- 【RAM & Storage】The firewall router equipped with 8G DDR3 RAM, max support 8GB; 128GB mSATA SSD, up to 512GB. Not support HDD. Size:5.27 * 4.98 * 1.43 inches, Weigh:500g, small but powerful.
- 【12 Months Service】You will get a firewall pc and accessories，If you encounter any problems during the use, please contact us through Amazon, we have a professional and efficient team dedicated to serving you.
The tutorial shows Production exposed to the Developer Portal by default. It also notes that organizations created before April 24, 2025 may have Development exposed by default. Environment exposure is an organization-level setting, so confirm which environments are exposed in your own organization before you publish. Otherwise, a test API may reach consumers unintentionally, or a production API may stay hidden.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choreo Connect is a different gateway
Choreo Connect appears in WSO2 API Manager documentation as a separate gateway deployment option. The WSO2 API Manager 4.1.0 docs describe it in two ways: as a gateway that works with API Manager, and as a standalone gateway managed with APICTL. These are versioned API Manager instructions, not a guide to adding the managed Choreo API Gateway to a Choreo project.
Read the Choreo Connect material only if your architecture runs API Manager or a self-managed gateway. For a service that lives in Choreo, the endpoint and proxy routes described above are the relevant path.
Sources
- WSO2, “Expose a Service as a Managed API” (proxy creation, deployment, testing, promotion, publication, and invocation).
- WSO2 Choreo documentation, “Configure Endpoints” (endpoint attributes, visibility, buildpack configuration, gateway exposure, and protocol limits).
- WSO2 Choreo documentation, “Develop an API Proxy from Scratch” (proxy concept and API management features).
- WSO2 Choreo documentation, “Develop a Service” (component configuration context).
- WSO2 API Manager 4.1.0, “Choreo Connect Overview.”
Choreo’s console, endpoint behavior, and environment defaults change over time, so confirm the current behavior in your organization before you deploy.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
