Overview
Two identical environments on AWS, fixed monthly support, and optional extras you can add when you need them.
Staging and production on AWS, publishing pipeline, Claude access, Google sign-in, handover. Details in section 03.
Security, updates, performance, technical SEO, monitoring and a monthly report. Details in section 04.
Staging and production together, paid to AWS at cost. Details in section 06.
What we build is yours to run, extend or hand off. The code lives in your GitHub, and the infrastructure is defined as code and runs in an AWS account you own. Optional extras are in section 05: WordPress content migration, website redesign and build, single sign-in licence, DigitalOcean instead of AWS.
Roles
As discussed on the call: we maintain the engine, you own the content.
Seeders
- Content and publishing: what goes live and when
- Appearance and pages, built from components in Strapi
- Forms and their follow-up
- SEO strategy
- The new website and its design, unless you add option B
- Content migration from WordPress, unless you add option A
Artkai
- Infrastructure and hosting on AWS
- Security and dependency maintenance
- Strapi updates, checked on staging before production
- Performance and technical SEO, including Core Web Vitals
- Monitoring and incident response under the SLA
- Monthly report on what changed
The team
| Role | Status | What they do |
|---|---|---|
| Cloud / DevOps engineer | Proposed | Builds both environments, the publishing and deploy pipelines, security and monitoring. Runs the monthly maintenance. |
| Strapi engineer | Proposed | Production Strapi configuration, Claude access through API and MCP, admin sign-in, Strapi updates. |
| Project lead | Proposed | Kickoff, status, acceptance, and the monthly report. Your single point of contact. |
Setup
One fixed fee of $11,700. Staging and production are built from the same code, so what you test is what goes live.
How publishing works
Visitors get static files from the CDN and never reach Strapi. The admin stays closed to the public, the site stays fast, and the database stays small.
How Strapi updates reach production
What is included
APP_KEYS, JWT, database password) in a vault.cms. and cms-staging. domains. Health checks and logs.Access to your GitHub and test Strapi, a decision on sign-in, access to DNS, and a frontend that builds to fully static files. These four set the pace more than our own work does.
Monthly support
Starts at $1,500 per month for the basic maintenance package. Every update is tested on staging before it reaches production.
What the package covers
npm audit.Not in the basic package
- Design and frontend changes
- New content types and other development in the CMS
- Content entry and SEO strategy
- Major Strapi upgrades, for example v5 to v6, estimated separately
- 24/7 on-call for P1 issues, quoted on request
- Questions beyond 4 hours a month, quoted before we start
SLA
Support hours: Monday to Friday, 9:00–18:00 CET.
| Priority | Example | Response | Resolution or workaround |
|---|---|---|---|
| P1 · Critical | Site or admin unavailable, critical vulnerability | 1 hour | 4 working hours |
| P2 · Important | Publishing, API or part of the admin does not work | 4 working hours | 1 working day |
| P3 · Normal | Questions, advice, small configuration changes | 1 working day | 5 working days |
Options
Add them now or later. Each one is priced on its own and stays out of the base package.
A · WordPress content migration
You plan to migrate content yourselves. We can do it for you; the final price is fixed after the inventory.
- Inventory: post types, taxonomies, custom fields, media, volume
- Mapping from the old structure to your new content types
- Export and transform scripts: HTML and shortcode cleanup, components and dynamic zones
- Media transfer to S3 and link replacement
- Pilot with a few records of each type, then your review
- Final import, count check and spot checks
- Map of 301 redirects from old URLs to new ones
Sized for roughly 100–300 records. We reprice if the volume is larger.
B · Website redesign and build
We understand your team is building the new site. If you want us to do it, we redesign the site and build the frontend.
- Redesign of the website
- Frontend build, exported as fully static files
- Integration with Strapi components and your publishing flow
- Final price within the range after we agree the page count and scope
C · Single sign-in licence
Strapi Growth with the SSO add-on: Google sign-in directly in Strapi, no second password.
- 3 seats included, extra seats are priced by Strapi
- Includes Content History (14 days), Releases and Live Preview
- Without Content History, an unwanted edit by a person or by Claude can be undone only by restoring the database
D · DigitalOcean instead of AWS
Same architecture on your DigitalOcean contracts: App Platform, managed PostgreSQL, Spaces with CDN, Cloudflare as the firewall.
- Infrastructure ≈ $65–90 a month for both environments, instead of ≈ $153 on AWS
- Google sign-in in front of the admin is not available here, so you choose the licence from option C or a community plugin
- Monthly support price stays the same
Hosting on AWS
Two environments, staging and production, identical in code. AWS bills you directly for what they use.
Cost by service, $ per month
| Service | Production | Staging |
|---|---|---|
| Strapi container, ECS Fargate, 0.5 vCPU / 1 GB, ARM | 14.42 | 14.42 |
| Public IP for the container | 3.65 | 3.65 |
| Load balancer with two public IPs | 24.31 | 24.31 |
| Database, PostgreSQL, single zone, 20 GB | 13.98 | 13.98 |
| Firewall, 5 rules | 10.30 | — |
| CloudFront flat-rate plan | 15.00 | 0.00 |
| Secrets, logs, storage, container registry | 5.60 | 4.10 |
| Per environment | ≈ 87 | ≈ 60 |
| Shared by the account: DNS, threat detection, audit log, budgets | ≈ 5 | |
| Both environments, per month | ≈ 153 | |
AWS list prices for us-east-1, November 2026, a month counted as 730 hours. A European region adds 10–20%. On the call we mentioned $25–30 per environment. That figure covered only the container service and the database, without the load balancer, firewall and CDN plan. GitHub Actions minutes for builds in your private repository are billed by GitHub.
Sizing
One load balancer shared by staging and production, split by domain. The environments are less isolated.
Two separate environments as in the table: no NAT gateway, no multi-zone database, firewall on production.
NAT gateway, multi-zone database, 1 vCPU / 2 GB, a separate firewall on CloudFront. More than an admin without public visitors needs.
Timeline
About 4–6 weeks from access to launch. Dates are confirmed at kickoff.
Next steps
Tell us a kickoff date and answer the questions below. Short answers are enough.
What we need to start
- A kickoff date
- Access to your GitHub and your test Strapi
- AWS or DigitalOcean, and an AWS account decision
- Access to your DNS, and who handles 301 redirects from the old site
- Who writes the requirements for the content model and acceptance
Setup is a fixed fee. Support is a fixed monthly package. AWS hosting is paid to AWS at cost. Options are priced on their own. Options A and B get a final price within their range after we agree the scope.
Questions for you
- Which framework is the new frontend built in, and who builds it? Can it export fully static files, and how long does a build take? Who fixes the build if it fails because of frontend code?
- Where should form submissions go? Do you need draft preview before publishing?
- Do editors work only in production, with staging used to check updates? Or do you need a staging → review → production flow?
- Which Strapi version (v4 or v5), plugins and database does your test environment use? Do we move it to AWS as is?
- AWS or DigitalOcean? A new AWS account that we hand over to you, or your existing one? Which region, and are there rules on where data is stored?
- Is Google sign-in in front of the admin plus a Strapi password fine, or do you want single sign-in with the licence from option C?
- How does Claude connect: claude.ai, Claude Desktop or Claude Code? Do you want API access restricted by IP?
- What do you expect from the SLA: hours, response time, time zone?
- When do you plan to launch, and who handles 301 redirects from the old WordPress URLs?