Pull Request as a Service
Only pay for code you merge
With GitStart, you’re always in charge. Every PR comes with a cost in credits. Credits are consumed when you merge PRs. This aligns incentives and ensures quality.
Speaks all the languages you love
GitStart works with most technologies used by fast growing engineering teams. The acceleration is especially fast for JS related frameworks (Node, React, Next, etc), and engineers have also used it to build compilers in C++.
No management, just code
You don’t have to speak with anyone to use GitStart. We send your task to multiple engineers, have them review each other, and select the best PR. Ramp-up is fast: with SourceGraph, GitStart shipped 25 PRs in the first 20 working days.
No need to trust us with your code
Skip time consuming implementation.
Let GitStart accelerate you.
Assign tickets in parallel. Assign any task that takes <5 days of full time work and has a clearly defined acceptance criteria. Drop useful documents like design files for frontend and logic for backend.
Receive daily updates on each ticket. For more control, activate "scaffold mode" to get a scaffold PR detailing how we'll tackle the task, as well as a budget estimate.
Review pull requests. All PRs go through 2+ reviews. They come with a testing environment link and a loom video. Billing stops there: all fixes are free if within scope. RainforestQA integration coming soon!
See it for yourself with
open source PRs
Acceleration stories
"
Trying to code in an unfamiliar language by googling everything is like navigating a foreign country with just a phrase book. Using GitHub Copilot is like hiring an interpreter.
Jane Doe / CloseAI
"
Trying to code in an unfamiliar language by googling everything is like navigating a foreign country with just a phrase book. Using GitHub Copilot is like hiring an interpreter.
Jane Doe / CloseAI
"
Trying to code in an unfamiliar language by googling everything is like navigating a foreign country with just a phrase book. Using GitHub Copilot is like hiring an interpreter.
Jane Doe / CloseAI
"
Trying to code in an unfamiliar language by googling everything is like navigating a foreign country with just a phrase book. Using GitHub Copilot is like hiring an interpreter.
Jane Doe / CloseAI
"
Trying to code in an unfamiliar language by googling everything is like navigating a foreign country with just a phrase book. Using GitHub Copilot is like hiring an interpreter.
Jane Doe / CloseAI
Under the hood
Military-grade security
On top of GitSlice, GitStart can ensure military-grade security with features such as online IDE (in partnership with GitPod) to ensure code never leaves your systems, as well as NDA signatures and personal audit logs for every GitStart engineer.
Review Environments. Even for native mobile apps
Each PR gets deployed in its own environment on every change. It supports docker containers to deploy web and backend projects. It can also deploy APK format for Android and IPA format for iOS projects to support native mobile projects.
Optimal talent allocation
Engineers are dynamically added and removed from an instance depending on their instance performance score. The highest performing engineers all get allocated full time to limit context switching.
Review driven development
All tickets are reviewed by 4 types of engineers. Owners review architecture and ensure integration. Developers code. Reviewers review. QA test edge cases. Role allocation for engineers averages 50% development, 30% ownership and reviews and 20% QA.
By devs for devs time tracking
GitStart custom time tracking tool is automatic - based on git branch & activity, non invasive - no screenshots, and fair - PR credits estimates discard meetings, breaks, etc to only include productive time (time spent speccing, coding and reviewing).
Lightning speed onboarding
When a GitStart instance capacity increases, we automatically create separate development environments, send the same tasks to hundreds of engineers, and have them review each other. Highest-ranked engineers earn the right to tackle new tickets.
Powered by the GitStart Community
Learn with the best
1. Hack on the codebases of the fastest growing companies worldwide.
2. Learn with coding tasks scoped by senior engineers.
3. Put your work in the hands of millions of users.
Accelerate your growth
1. Bi-weekly 1:1 call with experienced mentors.
2. Professional training: English coaching, technical courses, etc.
3. Extreme emphasis on code reviews from day one.
Remote done right
1. Receive payouts in your local currency.
2. Meet amazing engineers from all around the world in regular online events.
3. Work flexibly in a culture that embraces asynchronous communication.
Frequently
asked questions
What is GitStart great for?
GitStart is best used for tickets that are easy to scope and review. Examples:
- Tech debt: converting JS into TS, increasing test coverage
- Front-end: building React components
- Backend: building an API endpoint, building an isolated function of a compiler
Tickets that are not a good fit for GitStart
GitStart is not a fit when tickets are hard to scope and review, such as tickets that:
- Are not achievable within 5 days of full time work
- Fill in a knowledge gap: anything you are not able to do yourself and therefore review
- Require getting on a call
- Are not about writing code
How precise do ticket specs have to be?
Engineering teams that have gone partially or fully remote typically don't need to change how they write specs. Good tickets:
- Are completable within 5 working days by a full-time developer
- Include a clear acceptance criteria (including edge cases)
- Provide all required assets/secrets/designs
- Can be executed in isolation, aka with limited to no dependencies
See real examples at this link
What technologies are supported?
GitStart works with most modern technologies used by VC backed ventures. Acceleration is especially fast for JS frameworks and libraries (Node, React, Next, Vue, vanilla JS, Typescript, etc), but engineers have also used it to build things like a compiler in C++. Send us a message if your technologies are not mentioned in this non-exhaustive list.
What tools do you integrate with?
- Ticketing system: all major ones, such as Jira, Github Issues and Linear
- Git provider: GitHub, GitLab, BitBucket.
If yours is not in this list, let us know. Building an integration typically takes less than a week.
How quickly can GitStart scale up or down?
Capacity automatically scales up and down with your needs. Automated coding competitions with hundreds of engineers mixed with automated code reviews and code pairing matching typically enable GitStart to double capacity every two to three weeks.
Do I need to speak with anyone?
No interaction is required. At the same time, engineers powering the GitStart are available if need be.
Who owns the code GitStart writes for me?
We are buddhism influenced engineers — we want to do things right. The code GitStart generates belongs to you. GitStart voids 100% of its intellectual property to all code, forever and for all jurisdictions. Terms and conditions are intentionally written to strongly favour users to make legal back and forth unnecessary.
How safe is my data?
Your data is safe as GitStart developers can never access it. A hard requirement to use GitStart is to have a staging environment.
Your code is safe with GitSlice (see "No need to trust us with your code" section).
Your tickets are safe. We only pull in the tickets assigned to us.
Can you fulfil enterprise level security requirements?
Yes. GitStart powers enterprise clients in industries like finance, insurance and blockchain.
On top of GitSlice, GitStart can ensure
military grade security with features such as online IDE development, in partnership with GitPod, to ensure code never leaves your systems, and NDA signature + personal audit log for every engineer.
How do you define "good code quality"?
We don't, you do.
You only pay for PRs you merge. If a PR does not meet your quality standards, you are welcome to reject it or add review comments.
Billing stops at the first review cycle: all updates and bug fixes, as long as they are in scope, are free. On average, 85% of PRs are merged within the first review cycle, which is slightly higher that our users' internal teams' average.
How do you ensure consistent code quality?
Quality is ensured in two main ways:
Optimal talent allocation: Engineers are dynamically added and removed from an instance depending on their instance performance score. The highest performing engineers all get allocated full time to limit context switching.
Review driven development: GitStart uses review driven development All tickets are reviewed by 4 types of engineers. Owners review architecture and ensure integration. Developers code. Reviewers review. QA test edge cases. Role allocation for engineers averages 50% development, 30% ownership and reviews and 20% QA.
What if GitStart introduces bugs?
All updates and bug fixes, as long as they are in scope, are free.
How does billing work?
Top up credits. Every PR comes with a credit estimate based on productive hours. Billing stops during the first review cycle - all bug fixes and updates are free, as long as they are in scope and reported within 1 week of PR submission. Your credit balance is only deducted when you merge a PR. Unused credits roll on forever and are fully refundable.
What are productive hours?
We couldn't offer enough transparency and fairness with off the shelf tools, so we built our own time tracking technology to differentiate productive hours (hours spent speccing, coding and code reviewing) from the rest (meetings, learning, breaks, etc). Our estimates only ever include productive time.
Also, productive hours are converted into mid-level engineer productive hours using each developer's performance coefficient.
Do credits expire?
Unused credits roll on forever and are fully refundable.
"GitStart is one of the worlds top 20 companies shaping the future of remote work"
“We invested in Gitstart because they are solving tough problems."
“They allow developers to do small coding tasks and get paid from home.”
