Home / Companies / Ona / Blog / May 2025

May 2025 Summaries

10 posts from Ona

Filter
Month: Year:
Post Summaries Back to Blog
Thin VDIs, paired with developer-first environments like Gitpod, offer a cost-effective and secure solution for enterprises with global contractor workforces. Traditional VDIs create significant pain points for development, including non-persistent environments, incompatible tooling, and security scanning consuming resources needed for development. The thin VDI + Gitpod approach eliminates this tradeoff, delivering both robust security and effective development capabilities in a single, cost-efficient solution. Thin VDIs are more cost-effective, easier to manage, and security-focused, while Gitpod provisions purpose-built development environments that run directly in the AWS account, reducing costs and ensuring developer productivity.
May 22, 2025 1,264 words in the original blog post.
Luminus, a major electricity producer in Belgium, has addressed challenges faced by its data teams by implementing Ona's Enterprise solution, which operates on Amazon Web Services (AWS). Previously, the team dealt with issues related to managing dependencies and processing power, often encountering problems with Amazon SageMaker's platform changes and long startup times. By switching to Ona, Luminus has established stable, reproducible Python development environments that facilitate the onboarding of new team members and streamline data processing tasks. This has resulted in significant cost savings, improved productivity, and enhanced security through fine-grained access control and single sign-on capabilities. The seamless integration with AWS services allows data engineers and scientists to efficiently transition from experimenting in Jupyter Notebooks to building in a proper IDE without additional setup, fostering better development practices. With Ona, Luminus has optimized its data processing workflows and reclaimed time previously spent troubleshooting, allowing the platform team to focus on future advancements like Generative AI.
May 21, 2025 1,638 words in the original blog post.
The article highlights the growing concern of AI security gaps in software development, where generative AI coding tools are creating new vulnerabilities and risks. The core issue is architectural, as most AI tools run on local developer machines, making it challenging for enterprises to see or control them. This has introduced a class of risks, including insecure package installation, credential exfiltration, and untraceable agent behavior. The article also mentions that 36% of code suggestions from GitHub Copilot had vulnerabilities, and that attackers can exploit these tools to infiltrate the software supply chain. To address this issue, the Cloud Security Alliance recommends sandboxing and runtime validation for AI-generated code. The article then presents Gitpod as a solution, providing a controlled, transparent, and resilient platform for AI-assisted development, which closes the AI security gap by providing a secure substrate for AI-assisted software development.
May 20, 2025 1,685 words in the original blog post.
AI coding assistants have transitioned from being a novelty to a necessity, with 97% of enterprise developers using them, which enhances productivity but also introduces security vulnerabilities, such as developers inadvertently exposing sensitive data or integrating insecure code. The inherent architectural issue is that most AI tools operate on local developer machines that lack visibility and control, which can lead to risks like insecure package installation and data leakage. Studies have shown that AI-generated code, such as from GitHub Copilot, often contains security flaws, and data leakage incidents have led major companies like Samsung to ban the use of tools like ChatGPT. Gitpod offers a solution by providing a secure platform with standardized, ephemeral, and isolated environments that ensure compliance and reduce the risk of AI-related security breaches. The platform integrates features such as fine-grained access management and real-time monitoring to safeguard against threats, offering a zero-trust foundation for AI development. This approach not only mitigates security risks but also enhances developer productivity and reduces costs, making Gitpod a preferred platform for AI-assisted development.
May 20, 2025 1,640 words in the original blog post.
The adoption of GitHub Copilot, an exceptionally powerful assistant for Visual Studio Code, requires a secure development environment to maintain the balance between empowering teams to innovate and ensuring security. Enterprises face pressure to adopt AI tools while maintaining security standards, which can result in significant business risks such as intellectual property leakage, compliance violations, and data breaches. To address this challenge, enterprises must lay a secure foundation by implementing guardrails for sensitive projects, achieving secure code quality, and securing developer devices. This involves understanding the security implications of using GitHub Copilot's AI features, ensuring proper identity and authentication, monitoring agent actions, and enforcing repository-level editor access controls. By adopting secure development environments like Gitpod, enterprises can implement defense-in-depth strategies that contain the risk of adopting assistants like GitHub Copilot while getting the AI benefits. This approach enables organizations to confidently scale their AI adoption from experimental pilots to enterprise-wide implementation, maintaining security and compliance while unlocking the transformative power of AI coding agents.
May 19, 2025 1,762 words in the original blog post.
Windsurf, an AI code editor built on top of Visual Studio Code, offers a powerful tool for developers but requires secure development environments to ensure the balance between innovation and security. Adopting Windsurf without implementing guardrails can lead to significant business risks, including intellectual property leakage, compliance violations, and data breaches. To mitigate these risks, enterprises must establish a secure foundation by implementing data governance, identity and authentication measures, achieving secure code quality, and ensuring secure developer devices. This requires comprehensive infrastructure changes, including enforcing repository-level editor access controls, monitoring AI agent actions with audit trails, standardizing agent setup, and implementing zero-trust network security for agents. By doing so, organizations can confidently scale their AI adoption while maintaining security and compliance.
May 19, 2025 1,792 words in the original blog post.
The adoption of AI editors like Cursor in enterprise environments requires a secure foundation to balance innovation with security risks. This involves implementing data governance, identity and authentication controls, ensuring code quality and security, and securing developer devices. Enterprises must consider how to classify sensitive IP, maintain audit trails, enforce editor settings consistently across environments, restrict access to specific codebases, and ensure secure deployment of AI tools. Running Cursor within a secure development environment like Gitpod can provide defense-in-depth strategies that contain the risk of adopting editors while getting the AI benefits. This approach enables organizations to harness AI's full potential while maintaining security and compliance.
May 19, 2025 1,788 words in the original blog post.
Gitpod is a comprehensive development environment that provides secure, scalable, and context-rich infrastructure for artificial intelligence (AI) to succeed. It offers fast, pre-configured environments with the right code, tools, and permissions baked in, enabling agents to operate effectively. Gitpod ensures secure connections, scales with growth without increasing risk, amplifies developers' capabilities, runs on infrastructure rather than plugins, and serves as a critical link between internal developer portals and AI strategies.
May 13, 2025 454 words in the original blog post.
The software conductor's handbook aims to help developers transition from manual coding to orchestrating AI agents, focusing on maximizing autonomy for AI software development agents. It highlights the limitations of current approaches and introduces techniques for achieving greater agent autonomy, such as creating detailed 'agent PRDs' (Product Requirements Documents) that include goals, code snippets, and step-by-step implementation details. These documents enable developers to work with AI agents in a more productive and efficient manner, reducing the need for constant human intervention. The guide also emphasizes the importance of isolated development environments to ensure security, resource isolation, and scalability as agent fleets become increasingly common. By adopting these strategies, software conductors can unlock the full potential of their AI agents and drive developer productivity up.
May 08, 2025 2,420 words in the original blog post.
Software development is undergoing a transformative shift from manual coding to the orchestration of AI agents, with productivity increasingly measured by the "time between disengagements" of these agents. This paradigm shift calls for developers to transition from a code-centric mindset to one of a "software conductor," coordinating multiple AI agents capable of executing complex tasks autonomously. To maximize agent autonomy and effectiveness, developers should craft detailed "agent PRDs" (Product Requirements Documents) that outline goals, current implementations, proposed solutions, and step-by-step implementation plans. Such structured guidance enhances the agents' ability to work independently, reducing the need for constant human intervention and allowing for parallelism in software engineering. The guide emphasizes the importance of using automated development environments to foster agent autonomy and security, thereby preparing developers for a future where fleets of AI agents operate in tandem, significantly enhancing productivity and scalability in software projects.
May 08, 2025 2,364 words in the original blog post.