Discover Stroa.io, the AI-powered IDE revolutionizing Apigee X and Hybrid development. Learn to automate complex proxy creation, simplify cluster operations, and validate APIs using local emulators and advanced AI blueprints.
Strofa.io is an independent, third-party desktop IDE for Google Cloud Apigee. Not affiliated with or endorsed by Google.
Q&A Recap
1. If we are in this tool, don’t we need to use Apigee UI at all?
The goal is to give developers the ability to fully develop locally with all the features available in the UI/UX and stay up to date with changes - including the flexibility to work in both Strofa and the official UI, whichever is more convenient for the developer. It’s not mandatory. Some new features in the official UI will come to Strofa within a month or two per our roadmap. We are not sponsored by or affiliated with Google - we are a third-party tool focused on accelerating the development process for developers.
2. Where is Strofa hosted and how can we plug it into Apigee X? Does it import already created proxies?
Connecting to an Apigee organization is possible via Google Account (SSO) or with a Service Account (JSON key).
3. Can you import OpenAPI spec and create policies from the spec?
Absolutely - importing an OpenAPI spec creates all operations automatically. Extensions currently in development will also attach policies to the appropriate flows/operations based on spec annotations like x-policy-apikey.
4. Does Strofa support Apigee OPDK version?
No - Strofa currently works only with Apigee X and Hybrid. With sufficient customer demand, OPDK support can be added to the roadmap.
5. Will we be able to integrate with API Portal?
Strofa is a development IDE - there is no portal integration at this time. However, there is integration with our other product, KALITVI HUB (hub.kalitvi.com).
6. What’s the pricing model?
There are several tiers (Development, Ops, and combined). Pricing starts at $99/month per developer per seat. Final pricing is discussed directly with the client - feel free to reach out for more details. For beta testers (30 spots available - subject to spots left), there is a free 90-day trial.
7. Can it support multi-org?
Of course - if a user has access to more than one organization, all are visible and you can switch between them seamlessly.
8. How does it handle versioning and Revisions when developing locally?
The latest draft version is kept locally (if saved).
9. Is there an option to choose LLM model and is it configurable?
Yes - Anthropic and Gemini models are currently supported. Support for OpenAI and other providers is planned.
10. Does the IDE connect to a git repo? One repo for all APIs or repo per API?
There are multiple strategies available: proxies in one branch with different subfolders, one proxy per branch, or a custom path within a branch.
11. How do merge and pull requests work if we use Git for versioning?
We push like regular code. Merge and pull request configuration is handled on the Git side - Strofa doesn’t impose any specific workflow.
12. Is there a free version to try out?
A free version will be available in mid-March, limited to the local emulator only (no Ops features or cloud connectivity).
13. Is documentation available?
The main feature overview is on the website (strofa.io). Detailed documentation is embedded directly inside the IDE in relevant places with tooltips and contextual hints.
14. Can it support multi runtimes across different regions?
For Apigee X (Cloud), this is transparent - deployment targets an environment which is bound to an instance. For Hybrid, multi-cluster support (Hybrid multi-DC) is in alpha and under active development.
15. How does deploy work if environment or organization is full (capacity restrictions)?
If capacity is exceeded, the Apigee control plane will reject the deployment from the IDE - same behavior as the official UI. Locally, there are no restrictions.
16. Can it generate OpenAPI spec for an existing proxy?
Yes - using AI, you can generate an OpenAPI spec based on the context of flows and operations.
17. Is there version control on the Hybrid config?
Yes - locally or in Git (config bundle).
18. How does installation and deployment integration with Apigee work?
It runs on the user’s local workstation - the IDE uses the local disk, Helm, configuration files, and so on.
19. What does the “I’m bored” button do?
It’s a built-in game to kill time while installation is running 
Next Steps
Continue the Conversation: Have questions about this session? Leave a comment below to discuss with the community.
Share Feedback: Let us know your thoughts on this TechTalk so we can improve future sessions → Feedback: Apigee Community TechTalks
Explore Further: Contact our sales team to see how these solutions fit your specific enterprise architecture → https://goo.gle/3OsGRJb
Stay Tuned: Subscribe to the YouTube channel and register for upcoming TechTalks → Google Cloud Apigee Community TechTalks