Frequently Asked
Questions

JetRockets is a senior Ruby on Rails company in New York. We build new products and MVPs, add features to live applications, upgrade and modernize aging Rails codebases, rescue stalled projects and fix AI-generated code, and design and build the web and mobile apps around them. Then we keep that software running in production. All of it is delivered through JetEngine, our AI-powered delivery system, either as a fully managed service or set up inside your own engineering team.

Our default stack is Ruby on Rails with Hotwire (Turbo and Stimulus). Where a product needs it, we use React or Svelte on the frontend. For mobile, we build with React Native, Flutter, and Hotwire Native. Our databases of choice are PostgreSQL and MySQL. We deploy on AWS, Google Cloud, Azure, and DigitalOcean.

We've worked with clients in healthcare & wellness, fintech, travel, legal tech, marketplaces, education, and nonprofit sectors. Our portfolio spans across all of these.

Yes — extensively. Notable integrations include OpenAI, Stripe, Plaid, Zoom, PayPal, Slack, GitHub, LinkedIn, HubSpot, Calendly, Twilio, DocuSign, DeepL, Mailchimp, Google Analytics, and many more. If you need it integrated, we've likely done it.

JetEngine is how JetRockets builds software with AI. It has four connected stages: the Idea Engine (requirements, edge cases, acceptance criteria), the Prototype Engine (clickable flows you review before anything is built), the Build Engine (implementation inside your architecture, with tests, security checks, and review gates), and the Ship Engine (CI/CD, monitoring, backups, and rollback). The stages share context, so the output of each one becomes structured input for the next. Senior Rails engineers step in wherever judgment is required and stay accountable for what ships.

Neither. JetEngine is not a proprietary AI model, a chat wrapper, or a Rails gem. It is our methodology, workflows, coding standards, and quality gates, applied to leading AI coding tools. If the underlying AI tools change, the JetRockets standards stay the same.

Used directly, an AI tool leaves you to decide what context matters, judge whether its answers are correct, work out what is missing, and decide whether the result is safe to ship. JetEngine handles those steps for you. It asks the product questions that matter, preserves context from idea to production, works inside predefined JetRockets standards for architecture, testing, security, and infrastructure, validates its output, and escalates decisions that need human expertise.

Yes. There are two ways to use it. Fully managed: we run JetEngine for you, you set priorities and approve outcomes, and we own delivery. Build and own: we set JetEngine up in your environment, train your team to run it, and stay on for support and oversight.

Fill out our contact form or email hello@jetrockets.com. We typically respond within a few hours to schedule an intro call. You're also welcome to book a call directly via Calendly.

A description of the business outcome you want, any existing documentation or mockups, and access to your codebase if you have one. You don't need a technical specification: JetEngine's discovery stage turns your goals into requirements and acceptance criteria with you.

No. You describe what you want in plain language, such as "add subscriptions" or "let customers invite an accountant". JetEngine surfaces only the decisions you're the right person to make, you review the requirements and a clickable prototype before anything is built, and you approve the outcome. Implementation, testing, security checks, and release gates are handled for you.

We typically kick off within 1–2 weeks of agreement signing, depending on team availability and project scope.

Yes, always. We respect confidentiality and are happy to sign an NDA at any stage — before sharing any details about your project if needed.

You do. All intellectual property — code, designs, and assets — belongs to you once payment is complete. No lock-in, no strings attached.

Engagements start with a one-time setup of JetEngine on your product for a defined outcome, followed by a flat monthly service for ongoing delivery, operation, and maintenance. QA and DevOps are always included, and we don't bill hours. Audits have a fixed scope and are quoted up front, and design services are priced separately. We scope pricing on a call once we understand what you need.

We don't publish a minimum. The smallest way to start is a free Rails code audit, and paid audits have a fixed scope quoted up front. Larger work starts with a one-time setup followed by a monthly service, scoped on a call.

It depends on what you are building. Setup ends with your first release in production, and we commit to a timeline after the assessment, once we understand your product. After that, changes ship continuously.

No. You pay the agreed setup and monthly service, plus any third-party tools you explicitly approve and infrastructure such as hosting. No surprises.

Every piece of work runs through JetEngine's four stages. Idea: we turn your goal into requirements, edge cases, and acceptance criteria. Prototype: you review clickable flows and correct misunderstandings before anything is built. Build: AI coding agents implement the work inside your architecture and our standards, with tests, security checks, and review gates. Ship: changes are deployed with monitoring and rollback in place. We agree priorities with you each month, changes ship as they are ready, and you see a demo before each release.

Work is tracked in Asana, or in your own tools if you prefer, with priorities agreed each month. You have full visibility into progress at every stage.

Quality is built into JetEngine rather than checked at the end. AI works inside predefined JetRockets coding conventions, architecture patterns, and security rules. Every change passes automated tests and review gates, high-risk changes trigger review by a senior engineer, and you see a demo before each release. We also offer a 30-day bug fix guarantee: any bugs found in the first 30 days after launch are fixed free of charge.

Yes. We're experienced in inheriting legacy codebases and continuing from where prior teams left off. We begin every takeover with a technical audit to assess the health of the existing code before scoping any work.

Yes. Because JetEngine handles much of the execution, shipping more doesn't mean adding headcount at the same rate. We adjust the monthly service as your roadmap grows or settles.

Yes — Rails upgrades and legacy modernization are a core service. We handle version-by-version upgrades with full test coverage, zero-downtime deployment, and a detailed plan before any work begins.

A deep dive into load times, memory usage, query optimization (including N+1 detection), server configuration, background job performance, and caching strategy — delivered as a prioritized list of actionable recommendations.

Yes. We integrate AI features including GPT-based assistants, natural language processing, predictive insights, RAG pipelines, and automation workflows — built reliably into your Rails application, not just bolted on.

We'll help you decide based on your target audience, budget, and goals. We also offer cross-platform solutions with React Native, Flutter, or Hotwire Native — covering both platforms from a single codebase where appropriate.

We provide scalable, secure, and maintainable Rails support including version upgrades, architecture reviews, DevOps, security audits, and long-term platform partnerships. Enterprise clients typically work with us through an ongoing monthly service, either fully managed or with JetEngine set up inside their own team.

Yes. Running your software in production is part of the monthly service. JetEngine's Ship stage covers monitoring and alerts, backups and rollback, health checks, and maintenance, and new features keep flowing through the same process. We don't disappear after go-live.

Any bugs identified in the first 30 days after your product launches are fixed free of charge. This covers bugs in features we built — not new feature requests or issues introduced by third-party changes.