Your code kept current. Your production watched.
Two monthly agreements you sign from the control panel. Code Maintenance keeps dependencies and security patches up to date as pull requests you review. Managed Operations watches production, answers its alerts and runs deploys on request.
- 2 agreements to choose from
- None minimum term
- 30 days notice to end
- Yours everything we produce
# as signed in the control panelplan Code Maintenanceterm month to monthnotice 30 dayssigned contract ready to download
- deps: monthly updatespull request
- security: critical patchout of cycle
PLANS
2
Code Maintenance and Managed Operations
TERM
Monthly
No minimum term unless you choose one
RESPONSE
1business hour
To acknowledge a production outage, on Managed Operations
SIGNED
Online
In the control panel, by the project's biller
The agreements
Two kinds of ongoing work
Sign either one, or both. Each covers the work below and nothing else, and its full terms are shown in the control panel before you sign.
Code Maintenance
We keep your application's dependencies current and its security patches applied, every month, as pull requests you review and merge.
- Monthly dependency and security updates opened as a pull request on your repository
- Your test suite and a staging deploy run against every update before it reaches you
- Runtime and base image upgrades, with the breaking changes written up
- Critical vulnerabilities picked up out of cycle, not held for the next month
Month to month · 30 days' notice
Managed Operations
We watch your production environment, answer the alerts, and are on the other end of the line when something breaks.
- Alerting on availability, error rate and resource pressure, configured and maintained by us
- One hour response to a production outage, during business hours
- Deploys and rollbacks run by us on request
- A written report each month: incidents, capacity, what to do next
Month to month · 30 days' notice
Self-serve
Signed in three steps
Agreements live in the same control panel as everything else in your project, and are signed there.
- 01
Run something on Cosmoner
An agreement is added to your project's existing subscription, so the project needs at least one paid resource first: an app, a server, a database or anything else you run here.
- 02
Read the terms and pick a term
Open Agreements in the project. Each plan shows its monthly price and its full terms before you commit, and you can paste a discount code if you have one.
- 03
Sign with your name
The project's biller signs by typing their full name. The agreement starts that day, and a copy of the contract is ready to download or print.
What every agreement carries
A real contract, without the paperwork
The same terms apply to both plans: how they bill, how they end, and who owns the work.
Signed in the control panel
Nothing to print, sign and post back. The biller reads the terms, types their name, and the agreement is in force.
Projects → Agreements
A contract you keep
Every signed agreement has its own document: the parties, the fee, the term and every clause. Download it or save it as a PDF whenever you need it.
English and Swedish
Terms and price kept as signed
The clauses and the monthly fee are recorded on your agreement the day you sign. Later changes to a plan apply to new signatures, never to yours.
Versioned terms
Month to month
No minimum term unless you choose a commitment where one is offered. Give notice from the control panel at any time and the agreement ends 30 days later.
30 days' notice
On the invoice you already get
Billed monthly in advance on the project's subscription, next to everything else you run. The part-month you sign in is not charged.
Whole months only
Your code stays yours
Everything produced under the agreement, including every change to your repository, belongs to you. You grant the access the work needs and can take it back.
You own the work
What it costs
A fixed monthly fee per plan
No hourly billing for the work an agreement covers. You see the fee before you sign, and it stays what you signed.
- The monthly fee
- Per plan
- One fixed monthly price for each plan, shown in the control panel before you sign and printed on your contract. Nothing about it is metered.
- The month you sign in
- Not charged
- Work starts the day you sign, and the first full fee falls on your next invoice.
- A commitment period
- Optional
- Where a plan offers one, a commitment lowers the monthly fee for its length and then continues month to month. Both prices are shown side by side before you choose.
- Discount codes
- At signing
- Paste a code you were given when you sign. The reduced fee is shown before you sign and recorded on the contract.
- Ending it
- 30 days' notice
- Billing continues until the notice period, or a longer commitment, has run, then stops. Fees already paid are not refunded.
Agreements bill differently from resources: no proration and no credit when they end. Billing & Payments in the docs has the details.
Questions worth answering up front
Anything else about an agreement, or work it does not cover, is a message away.
- Can I sign one myself?
- Yes, from Agreements in your project's control panel. The project's biller signs, which is the project owner unless billing has been handed to someone else, and the project needs at least one paid resource so there is a subscription to add the agreement to.
- Is there a minimum term?
- No. An agreement runs month to month unless you choose a commitment period at signing, where the plan offers one. You can give notice at any time: it ends 30 days later, or when the commitment ends if that is later, and is billed up to that date.
- Who merges the changes?
- You do. Code Maintenance delivers its work as pull requests with a written summary, and Managed Operations runs deploys and rollbacks when you ask but never merges your code. An update that would mean rewriting your code comes to you with an estimate first.
- What happens outside business hours?
- Managed Operations commits to acknowledging a production outage within one business hour, where business hours are 09:00 to 17:00 CET on Swedish working days. Outside them the agreement carries no response commitment. It covers resources running on Cosmoner, not anything hosted elsewhere.
- What is not included?
- Changes to what your application does. New features, migrations and incident work beyond the included response are quoted separately before any of it starts.
- Can I hold both agreements?
- Yes. Each plan is signed on its own, and a project can hold one agreement of each plan at a time.