PermaShip
An autonomous engineering platform whose specialized AI agents scan a connected Git repository around the clock. An executive agent, Nexus, arbitrates every proposal and alone opens tickets. Supervised or autonomous, it delivers reviewable pull requests from 20 USD monthly.
What is PermaShip?
PermaShip is an autonomous engineering platform: a roster of AI agents, each specialized in one domain, runs continuously against a connected codebase instead of waiting to be prompted. The product page names nine of them, CISO for security, SRE for reliability, QA for test coverage and CI/CD for pipeline health, plus Performance, FinOps for cost, UX for front-end quality, Product Manager for scope alignment and AgentOps for the health of the agents themselves. Each is an expert in its own area and deliberately unaware of what the others are proposing.
The point of the product sits one level above them. Nexus is the executive agent, and it is the only one allowed to create a ticket: every other agent has to argue its case. Nexus weighs each proposal against the customer organization's strategic alignment, risk posture and values, and findings are cross-reviewed, so a security issue is stress-tested by the SRE and CI/CD agents before it moves forward. Two autonomy levels are offered: supervised, where proposals come back for human approval, and autonomous, where Nexus acts and then reports. Every approval, rejection and edit feeds an organizational memory that sharpens how Nexus reads the team's values.
The architecture has three parts. Control is the dashboard and API, with budgets and a full audit trail. Agents/Nexus is the governing intelligence. Runners are isolated containers, one per job, with disposable workspaces. An MCP Integration Gateway lets external tools be plugged into the execution context from the dashboard. There is no idle time by design: when the queue empties, agents keep scanning and pick up self-directed work such as latent bugs with a fix PR attached, vulnerable dependency patches, missing tests, dead code and technical debt.
PermaShip positions itself as a layer above execution tools rather than a replacement for them, and claims to serve technical and non-technical users alike. Nexus itself is published open source under the MIT license on the PermaShipAI GitHub organization, with 57 stars and 175 commits on main, and supports Claude, Gemini and OpenAI models. A Managed Engineering offer adds a PermaShip tech lead who drives the platform for you.
What it does
- Connect a Git repository to the platform
- Let domain-specialized agents scan the codebase continuously
- Receive proposals arbitrated by Nexus instead of a raw queue of pull requests
- Set the autonomy level, supervised or autonomous
- Define auto-approval criteria for low-risk work
- Take briefings in Slack or Discord
- Review and merge pull requests on your own schedule
When to use PermaShip / When not to
A quick filter to help you decide if PermaShip is the right fit.
When to use PermaShip
- Startup founders stretched thin between product, leadership and a backlog that only grows
- Scaling teams that need more engineering output than their hiring pipeline can deliver
- Engineering leaders sitting on open headcount while recruitment drags on
- Teams carrying chronically deferred work: technical debt, thin test coverage, security fixes, CI health
- Agencies and dev shops handling out-of-SOW work across client repositories, with governance kept separate for each client
When not to use PermaShip
- Developers shopping for an AI code editor: the site positions PermaShip against tools that execute an instruction on the spot
- Anyone who wants an assistant to prompt, since the platform advertises itself as prompt-free
- Teams that need to evaluate at no cost first: there is no free plan and no announced trial, and entry starts at 20 USD per month
- Users who rely on written documentation, because the /docs page still lists guides and API references as coming soon
- Anyone without a connected Git repository and a CI/CD chain, or anyone expecting a mobile app or a browser extension
How to use PermaShip
A typical end-to-end flow, from setup to results.
- Pick a tier on the pricing page: a modal asks for your email, then hands off to Stripe
- Connect a Git repository, which the site promises takes minutes and requires no new workflow
- Let the specialized agents start scanning immediately and submit their proposals to Nexus
- Set the autonomy level, supervised or autonomous, according to how much you want Nexus to do unaided
- Define auto-approval criteria per action type so low-risk work moves without you
- Review the proposals in the Control dashboard, or take briefings in Slack or Discord
- Approve the work, then merge the resulting pull requests on your own schedule
- For a scaling team, the site recommends starting on a single repository with success criteria agreed in advance, then measuring within a week
- Expect to work without installation documentation for now, since the /docs page is still an announcement
Pros & Cons
Pros
- An explicit governance layer: only one agent can create tickets, which bounds what ever reaches the repository
- Autonomy is a dial rather than a default, and supervised mode keeps a human approval in front of every execution
- Execution isolation is spelled out: one container per job, disposable workspaces and allowlisted outbound traffic
- Strong traceability, with immutable evidence bundles and exportable audit logs
- The company states it does not train models on customer code and does not keep source code beyond a job, and the terms leave ownership of generated code with the customer
- Public, readable pricing with a low entry point at 20 USD per month, plus unlimited seats and unlimited projects on every tier
- The Nexus core is published open source under the MIT license, and the home page carries a named, checkable customer testimonial from Adam Englander, CTO of Voltaire, Inc.
Cons
- No free plan and no announced trial, and fees are stated to be non-refundable, so any evaluation starts at 20 USD per month
- No public documentation to date: /docs lists guides and API references as coming soon, and the docs.permaship.ai subdomain returns a 404 error
- The /status page that the terms of service point to for service availability also returns a 404 error
- The contact page publishes an address on permaship.com, a domain whose null MX record means it accepts no email at all, and the same page still carries unedited HubSpot template links
- SOC 2 Type II is advertised as in progress rather than obtained, and no subprocessor list is published even though third-party model providers handle the code
- A very young vendor: the domain was registered on February 7, 2026, there is no Wayback capture, the blog stopped on April 4, 2026, and there is no postal address, no about page and no named team
- No hosting country or region is announced, data residency is reserved for enterprise accounts, integrations are capped at 5 on the entry tier, there is no mobile app or browser extension, and the terms set no minimum age
Pricing & Plans
There is no free plan and no free trial. The lowest paid entry point is 20 USD per month. Three public subscription tiers are published, at 20, 200 and 2,000 USD per month, billed in advance either monthly or annually. Consumption is metered in Compute, bought each month, with every ticket drawing on the balance according to its complexity: 1 to 3 Compute for a simple fix or test, 5 to 15 for a feature or an improvement, and 15 or more for a from-scratch build or a large refactor. Nexus governance, supervised and autonomous modes, a monthly Compute budget, unlimited projects and unlimited seats are included on every tier. The pricing page states that there are no setup fees and that customers may cancel at any time. Fees are non-refundable except where the law requires otherwise, and prices may change with 30 days' notice. Payment is processed through Stripe once an email address has been entered in a modal. The Managed Engineering offer sits outside the published grid and is quoted on request.
- 400 Compute included
- up to 100 tickets per month
- 1 concurrent job
- 30-day retention
- 5 integrations
- 4 GB of runner memory
- 4
- 000 Compute included
- up to 1
- 000 tickets per month
- 5 concurrent jobs
- 90-day retention
- 15 integrations
- 8 GB of runner memory
- 40
- 000 Compute included
- up to 10
- 000 tickets per month
- 20 concurrent jobs
- 365-day retention
- unlimited integrations
- 16 GB of runner memory
- a dedicated tech lead drives the platform for you
- under three engagement models (Burst SOW with a defined scope
- Managed Engineering Partner on an ongoing basis
- Department Partner tailored to the client)
- optional microVM isolation
- SIEM log export
- data residency controls and configurable limits
Data, GDPR & hosting
A consolidated view of how PermaShip handles your data.
GDPR overview
PermaShip publishes a privacy policy and terms of service, both dated February 7, 2026, and advertises GDPR-compliant data handling and deletion, with data processing agreements available. Depending on your jurisdiction, the policy lists rights of access, rectification, erasure, portability, objection and restriction, exercised by writing to privacy@permaship.ai. Cookies are split between essential ones served without consent and analytics (Google Analytics is named) served under consent, with a first-visit banner and a Cookie preferences link in the footer. Several pieces are missing: no Article 27 EU representative is designated, no data protection officer is named, no postal address is published, no subprocessor is listed, and no international transfer mechanism is identified, neither standard contractual clauses nor the Data Privacy Framework. The company is US-incorporated and its terms are governed by Delaware law.
Who owns the data?
PermaShip's terms of service state that you retain all ownership rights to your source code and data. Connecting a repository grants the company a limited license, restricted to accessing and processing that code solely to provide the service. Code and pull requests generated by PermaShip on your behalf are owned by you, with no carve-out for the vendor. The counterpart is stated just as plainly: you are responsible for reviewing any generated code before merging it, and PermaShip gives no warranty that what its agents produce is free of defects or vulnerabilities. Ownership here comes with the review burden firmly attached.
Reuse rights
PermaShip collects account details (name, email, company, role), usage data (job runs, API calls, features used), technical data (browser, IP address, cookies) and the source code it processes. Source code is accessed only for the duration of a job and is never kept beyond it. The stated purposes are providing and improving the service, executing jobs, transactional messages, support, trend analysis and legal obligations. Personal data is not sold. Three categories of recipients are described: infrastructure, analytics and support providers; third-party AI model providers working under data processing agreements; and authorities responding to a valid legal request. No individual subprocessor is named. The company states that your code is not used to train models or for any purpose beyond executing the jobs you configure. Outputs are yours to reuse without asking anyone, since generated code and pull requests are owned by you.
Data retention & training
Hosting summary
No hosting country and no hosting region is announced anywhere on the site, the service infrastructure is not publicly documented, and the domain is served behind Cloudflare. What is described in detail is isolation. Each job runs in its own isolated container, with no runtime shared between executions and disposable workspaces, so nothing persists from one run to the next. Optional microVM isolation is offered on the enterprise tier. Organization and project partitioning is applied at every layer, row-level security governs data access, and cross-tenant access is said to be prevented at the architectural level. Data is encrypted in transit with TLS 1.3 and at rest. Outbound traffic is restricted by explicit allowlists, and secrets are injected at runtime, never written to disk, to logs or into generated code. Source code is processed in ephemeral environments and is not retained once the job ends. Data residency controls exist, but only for enterprise accounts.
Things to keep in mind
Risks and trade-offs to weigh before adopting PermaShip.
- The terms of service require you to review any generated code before merging it, and the vendor gives no warranty that the output is free of defects or vulnerabilities, so treating pull requests as pre-approved is the fastest way to get hurt
- In autonomous mode Nexus acts without prior approval, which makes the autonomy setting the single biggest risk decision on this platform
- SOC 2 Type II is announced as in progress, and should not be read as a certification already obtained
- Third-party AI model providers process your code without being named, and no subprocessor list is published
- No hosting country or region is announced, and data residency controls are reserved for enterprise accounts
- Fees are non-refundable and there is no trial, so the evaluation itself is a paid commitment
- The contact address shown on the site, on the permaship.com domain, cannot receive email, so use the permaship.ai addresses or Discord instead; the vendor is under a year old, with no postal address and no published team
Setup & Integrations
Technical difficulty
Low to moderate. The site advertises setup in minutes: connect a Git repository, with no new workflow to adopt. The real prerequisites are a Git repository and, to get value from the CI/CD agents, a working continuous integration chain. PermaShip states that Nexus works for technical and non-technical users alike. The settings to think about are the autonomy level, auto-approval criteria per action type and Compute budgets. Custom Docker images, available from the Team tier, do require infrastructure skills. No installation documentation is published yet, and Managed Engineering exists for teams that would rather not drive the platform.
Deployment
Integrations
Behind PermaShip
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement PermaShip.
Frequently asked questions
How is PermaShip different from an AI coding assistant?
Is my code used to train AI models?
Who owns the code that PermaShip generates?
Can I stop the agents from changing my repository without approval?
How much does PermaShip cost?
How does Compute work?
Which integrations are available?
Is there any documentation?
Is PermaShip SOC 2 certified?
Is there a mobile app?
Should you pick PermaShip?
The product is real and checkable: a live Control app, an open-source core under the MIT license, a named customer testimonial from Adam Englander, CTO of Voltaire, Inc., and five customer logos on the home page. The value proposition is unusual and clearly stated, because PermaShip sells the governance of AI agents rather than their speed, and the rule that only Nexus may open a ticket is what makes that concrete.
What you have to accept is the rest of the picture. The vendor is very young: the domain was registered on February 7, 2026, the legal documents carry that same date, and there is no Wayback capture behind them. The public surface is unfinished, with documentation announced but absent, a status page that returns a 404 error, and a contact address on a domain that cannot receive email. Legal transparency is partial, with no postal address, no named team, no subprocessor list, and a SOC 2 Type II described as in progress rather than obtained. There is neither a free plan nor a trial, so evaluating the platform means committing 20 USD per month from the first day.
That trade works for a specific reader: a team that wants a second, governed engineering track running against its repository, that is willing to review every generated pull request, and that is comfortable betting on a company less than a year old. Teams that need audited certifications, published subprocessors and complete documentation before they sign anything are better off waiting and checking again once those pieces land.
- Choosing a selection results in a full page refresh.
- Opens in a new window.