Policies

Last updated: September 11, 2026 — added Business Email deliverability & anti-spam (SPF/DKIM/DMARC/PTR) section

Privacy Policy

Information We Collect

When you use Amemis, we collect the following types of information:

Account Information. Your name, email address, and billing details when you sign up.
Usage Data. Logs, deployment metadata, build output, and performance metrics related to your services.
Cookies. We use essential cookies for authentication and session management. Analytics cookies are optional.

How We Use It

We use your information to provide and improve the Amemis platform:

Provide the service. Process deployments, serve your applications, and manage your account.
Improve the platform. Analyze usage patterns to optimize performance and build new features.
Communicate. Send you service updates, security alerts, and relevant product announcements.

Data Sharing

We do not sell your personal data. We share data only with trusted third-party processors necessary to operate the service:

Stripe — payment processing (your billing info is handled directly by Stripe; we never store full credit card details)
AWS — cloud infrastructure and data storage
Cloudflare — CDN and DNS services

Each processor is contractually obligated to protect your data and use it only for the agreed services.

Data Security

We implement industry-standard security measures to protect your data, including encryption at rest (AES-256) and in transit (TLS 1.3), regular security audits, and strict access controls for our engineering team. Environment variables and secrets entered in the dashboard are encrypted and never logged in plaintext.

Your repository is your responsibility. Amemis reads configuration from your repository to build and run your app. If you commit a .env containing secrets to a public repository, those secrets are publicly readable and we cannot protect them — you must rotate anything exposed and make the repository private. See Your .env and Repository Visibility below for the required checks before deploying.

Your Rights

You have the right to:

Access the personal data we hold about you.
Delete your account and associated data at any time through the dashboard.
Export your data in a portable format.
Object to processing for certain purposes like marketing.

To exercise any of these rights, contact us at privacy@amemis.com.

Contact (Privacy)

If you have questions about this privacy policy, please reach out to privacy@amemis.com or write to our data protection team at Amemis, Inc.

Custom Domains

Custom Domain Setup

Amemis supports custom domains for your deployed applications, similar to platforms like Vercel and Netlify. You can connect any domain you own (purchased from Namecheap, GoDaddy, Cloudflare, Google Domains, or any other registrar) to your deployed service.

How It Works

Step 1: Add your custom domain through the Amemis dashboard (Deploy Apps → select your app → Settings → Custom Domain).
Step 2: Configure DNS records at your domain registrar to point to Amemis.
Step 3: Verify domain ownership through Amemis.
Step 4: SSL/TLS certificate is automatically provisioned (free, via Let's Encrypt).

Once verified, your app will be accessible at https://yourdomain.com with automatic HTTPS.

DNS Configuration

To point your domain to Amemis, add the following DNS records at your registrar:

A Record (recommended): Host/Name: @ or leave blank → Value/Points to: 204.168.174.49
A Record (subdomain): Host/Name: www → Value/Points to: 204.168.174.49
CNAME (alternative): Host/Name: www → Value/Target: your-app-name.amemis.com

DNS propagation typically takes 5 minutes to 24 hours depending on your registrar and TTL settings.

Namecheap

Log in to your Namecheap account at namecheap.com.
Go to Domain List and click Manage next to your domain.
Select the Advanced DNS tab.
Under Host Records, click Add New Record.
Select A Record. Set Host to @ and Value to 204.168.174.49. Set TTL to Automatic or 5 min. Click the checkmark to save.
Add a second A Record. Set Host to www and Value to 204.168.174.49. Save.
Return to the Amemis dashboard and click Verify Domain.

Namecheap note: If you see an existing CNAME record for www, you must delete it before adding the A record.

GoDaddy

Log in to your GoDaddy account at godaddy.com.
Go to My Products and click Manage next to your domain.
Click DNS or Manage DNS.
Under Records, click Add.
Select Type: A. Host: @. Points to: 204.168.174.49. TTL: 1 Hour or Quick. Click Save.
Click Add again. Type: A. Host: www. Points to: 204.168.174.49. Save.
Return to the Amemis dashboard and click Verify Domain.

GoDaddy note: GoDaddy may have default forwarding records. Delete any existing forwarding for @ and www before adding A records.

Cloudflare

Log in to your Cloudflare account at dash.cloudflare.com.
Select your domain from the list.
Go to DNS → Records.
Click Add record.
Type: A. Name: @. IPv4 address: 204.168.174.49. Proxy status: DNS only (gray cloud). TTL: Auto. Click Save.
Click Add record again. Type: A. Name: www. IPv4 address: 204.168.174.49. Proxy: DNS only. Save.
Return to the Amemis dashboard and click Verify Domain.

Cloudflare note: You must set the proxy status to DNS only (gray cloud) for the A record. If the orange cloud is active, the domain verification may fail because Cloudflare will proxy the traffic before Amemis can verify ownership.

Google Domains / Squarespace

Log in to your Google Domains account (now part of Squarespace at squarespace.com).
Select your domain.
Go to DNS → Custom records or DNS settings.
Click Create record.
Host name: @. Type: A. TTL: 3600. Data: 204.168.174.49. Save.
Create another record. Host name: www. Type: A. TTL: 3600. Data: 204.168.174.49. Save.
Return to the Amemis dashboard and click Verify Domain.

Other Registrars

For any other domain registrar (Hover, Porkbun, Dynadot, Name.com, AWS Route 53, etc.), the steps are the same:

Log in to your registrar's dashboard.
Navigate to DNS management or DNS settings for your domain.
Add an A Record with Host: @ pointing to 204.168.174.49.
Add a second A Record with Host: www pointing to 204.168.174.49.
If your registrar has an existing CNAME for www, delete it first.
Wait for DNS propagation, then click Verify Domain in the Amemis dashboard.

SSL / HTTPS

Amemis automatically provisions a free SSL/TLS certificate for your custom domain via Let's Encrypt once domain ownership is verified. No manual certificate installation is required. The certificate renews automatically before expiry.

If SSL status shows as pending, wait a few minutes and refresh. If it shows failed, verify that your DNS A records are correct and that no proxy (like Cloudflare orange cloud) is blocking verification.

Troubleshooting

Verification stuck on pending: DNS propagation may still be in progress. Use dig yourdomain.com or an online DNS checker to confirm the A record resolves to 204.168.174.49.
Verification failed: Ensure your A record points to 204.168.174.49 (not a CNAME or another IP). If using Cloudflare, ensure the proxy is disabled (gray cloud).
SSL failed: DNS must fully propagate before SSL can be issued. Wait 24 hours, then retry verification.
Site not loading: Confirm that both the A record for @ and www are configured. Check that you have not exceeded your plan's custom domain limit.

Business Email & Anti-Spam

Why emails land in Spam — and how to fix it

Fixed Sep 11, 2026 — DKIM for all business mailboxes. Our mail server now signs every outbound message with DKIM (mail._domainkey) for amemis.com and every connected business-email domain, and the records are kept in sync automatically. Independent checks (verifier.port25.com) report SPF="pass" and DKIM="pass" for each mailbox.

Email providers like Gmail, Outlook and Yahoo authenticate your messages using four DNS records about your sending domain. If one is missing, wrong, or mismatched, your mail is still delivered but is much more likely to be filed into the recipient's Spam folder:

SPF — a TXT record listing which servers are allowed to send mail for the domain.
DKIM — a cryptographic signature on every message plus a public key published in DNS, proving the mail really came from your domain.
DMARC — tells receiving servers what to do when SPF or DKIM fail, and sends you monitoring reports.
PTR / Reverse DNS — the name assigned to the mail server's IP address. It must match the sending hostname (mail.amemis.com). Gmail heavily penalizes a missing or mismatched PTR.

What Amemis manages for you automatically

For every domain using Amemis business email, these are configured on the mail server and in DNS:

MX:mail.amemis.com (priority 10) — routes incoming mail to your mailbox.
SPF:v=spf1 mx a ip4:204.168.174.49 ~all — authorizes our mail server (204.168.174.49).
DKIM:mail._domainkey.<yourdomain> — the signing key, auto-published and re-published whenever keys are rotated.
DMARC:_dmarc.<yourdomain> with p=none while your sending reputation warms up (we recommend p=quarantine after ~3 weeks of clean delivery).

Records to add at your registrar

The exact host names and values you need for any domain that points at Amemis business email (Namecheap: Domain List → Manage → Advanced DNS → Add New Record):

Type  Host                Priority  Value
MX    @                    10         mail.amemis.com.
TXT   @                               v=spf1 mx a ip4:204.168.174.49 ~all
TXT   mail._domainkey                  v=DKIM1; k=rsa; p=… (shown on the Business Email page)
TXT   _dmarc                           v=DMARC1; p=none; rua=mailto:postmaster@<yourdomain>.com

PTR / Reverse DNS (required for inbox delivery to Gmail & Outlook): open your server provider's panel (Hetzner: Network → Reverse DNS) and set the reverse record of 204.168.174.49 to mail.amemis.com.

Testing your setup

Send a test message to check-auth@verifier.port25.com. You'll get an automatic reply showing SPF=pass, DKIM=pass and DMARC results for your mailbox.
Send a test to your own Gmail/Outlook (not the one you send from), open it, and click Mark as not spam; also add the inbox address to Contacts. This teaches the mail provider that your domain is legitimate.
Start with friendly, low-volume mail and increase slowly — a brand-new domain or IP that suddenly sends hundreds of messages is one of the strongest spam signals.

Getting out of a Spam folder once flagged

Check the records above with a tool such as Google Admin Toolbox or dig +short TXT _dmarc.yourdomain.com — every record must return a result.
Temporarily send from one dedicated mailbox (hello@yourdomain.com) so the recipient adds one address to their address book / safelist.
Always check the Spam/Junk folder on both sides — a test message can land in the recipient's Spam with no error shown to you, and replies can be swallowed into your own mailbox's Junk folder. Open the webmail, open the Spam folder, and mark anything genuine as Not spam.
Avoid spam-trigger words, link shorteners, huge attachments, and images without text on your first campaigns.
After delivery rates stabilize (1–3 weeks), raise your DMARC policy from none to quarantine for stronger reputation.

Before You Deploy

Check Your Branch Before Deploying

Amemis builds and runs the branch you select when you create a service, and auto-deploy rebuilds and redeploys your app on every subsequent push to that same branch. The branch is therefore the single setting that determines what code is actually running.

Confirm the branch name before you deploy. A service created against the wrong branch — dev instead of main, a stale feature branch, or a fork — will build and serve that branch's code, and every later push to it will keep replacing your live app.
Once a service is created the branch is fixed. To move to a different branch, create a new service. Changing branches on a running service is not something we can undo for you, and the wrong branch can take your app offline until it is corrected.
Review your branch before every push. Auto-deploy acts on whatever is on the selected branch at that moment, including commits made by collaborators and by merge automation.

Deployments Are Non-Refundable

Once a deployment starts it cannot be cancelled, reversed or refunded. Amemis does not issue refunds for deployments, redeployments, or build attempts — including a deploy that fails, builds the wrong branch, or overwrites a working app with broken code. Check the branch and your configuration before you click, because after the build starts there is no undo.

Specifically:

Subscription fees and plan charges are non-refundable, as set out in Payment Terms.
Deployments, redeployments and auto-deploys triggered by a push are not separately charged while your plan includes them, and are not refundable where a plan quota or overage applies.
A failed build still consumes the build attempt; repeated failures are not credited back.
Rolling back means you deploy a known-good commit yourself — it is not an automatic refund or reversal, and it takes effect only once that build succeeds.

Your `.env` and Repository Visibility

The single most important thing to check before your first deploy is whether your repository is private and what your .env contains. Amemis reads your .env from the repository to configure your app, so a .env that contains real secrets is a real risk when the repository is public.

If your repository is public, everything in a committed .env is publicly readable. That includes API keys, database passwords, tokens, private service URLs and payment credentials. Anyone can clone the repository and read them, and search engines and archive services may retain copies even after you delete the file. Treat any secret that has been in a public repository as compromised and rotate it.

What you must do before deploying:

Make the repository private. This is the safest option and the one we recommend. Amemis supports private repositories on GitHub, GitLab and Bitbucket.
If it must stay public, remove every secret from .env and set those values in Dashboard → your app → Settings → Environment Variables instead. Dashboard values are injected at runtime and are never written into your repository.
Rotate any secret that was ever pushed to a public repository. Removing it from the latest commit is not enough — it remains in the history and must be treated as leaked.
Commit a .env.example with the required keys and no values, so the shape of the file is documented without exposing anything.

“Sync from .env” makes your repository’s .env the source of truth. With it enabled (the default), the values in your repo’s .env overwrite your dashboard environment variables on every push and redeploy. That makes a stale or wrong .env on your branch a live problem, not just a cosmetic one, so check the .env on the branch you are deploying before you deploy it. Amemis imports .env, .env.local and .env.production, and ignores .env.example.

Where Amemis stores your environment variables. Values you enter in the dashboard are stored in our database and injected into your app when the container starts. They are not committed to your repository and are not written into your app’s source tree on disk. Nevertheless, treat them as secrets: they are visible to anyone with access to your Amemis account, so do not share account access and use per-environment values rather than one shared production credential across environments.

Platform Troubleshooting

Auto-Deploy & the `.env` Problem

Fixed Aug 29, 2026 — self-healing deploys (all 20 apps). If you pushed to GitHub and the Amemis dashboard showed Git clone failed: ... Entry '.env' not uptodate. Cannot merge. that bug is now auto-healed. Every log and event now shows YYYY-MM-DD HH:MM:SS so you can verify the deploy time in Monitoring → Logs / Events.

What happened: Many apps (e.g. VerboCalls on branch VerboCalls-app) commit their .env to git. Amemis rewrites PORT=3027 (platform-assigned) via routes/env-import.js:102 syncEnvFilePort so the app listens on the correct port. That left a dirty working tree: git status reported clean (due to skip-worktree) while git reset --hard origin/<branch> failed — blocking every webhook-triggered redeploy until manual intervention.

How Amemis now fixes it:

Incremental update tries hard-reset:routes/deploy.js:336 cloneRepository now clears all skip-worktree / assume-unchanged flags (git ls-files -v), reset --hard HEAD, clean -fd, removes .env .env.local .env.*, checkout -f, then reset --hard origin/<branch>.
Fresh-clone fallback: If incremental still fails (corrupted index, etc.) the service directory is wiped and re-cloned --depth 1 — guaranteed to succeed on next push.
Webhook reconciliation: On every platform boot server.js:511 calls reconcileAllWebhooks() — all autoDeploy:true services are re-registered on GitHub/GitLab/Bitbucket, so a deleted webhook self-heals within 15 s.
All 20 existing apps were healed on Aug 29 (VerboCalls, Soundsdawn, Diapic, etc.) — no action needed unless you see a persistent building → failed loop.

What you should do (best practice — prevents future surprises):

Do not commit .env with secrets. Add it to .gitignore:

echo ".env" >> .gitignore
echo ".env.local" >> .gitignore
echo ".env.*.local" >> .gitignore
git rm --cached .env  # stop tracking without deleting local file
git commit -m "chore: stop tracking .env"
git push origin VerboCalls-app

Store secrets in Amemis Dashboard → App → Settings → Environment Variables or Monitoring → Settings → Environment Variables — they are injected via spawn env and via mergeEnvFileVars (user vars take priority over any .env in the repo).
Keep a committed .env.example or .env.template (without secrets) so teammates know required keys. Amemis only auto-imports .env, .env.local, .env.production and skips .env.example.
If you must commit .env, the platform will still handle it — just expect a short rm -f .env + reset on each deploy (visible as [ENV] Set PORT=… in logs).

Amemis App — Common Issues & Fixes

Below is a quick checklist for any app hosted on Amemis. All checks can be done from Deploy Apps → your app → Monitoring (Logs / Events / Metrics) which now shows YYYY-MM-DD HH:MM:SS for every entry.

1. Build fails — `npm install` / `Docker build` error

Symptom: Event Git clone failed → Build failed, logs show npm ERR or Dockerfile: …

Open Monitoring → Logs, filter BUILD — read the first [ERROR] line with timestamp.
Check package.json engines: Amemis runs node:20-alpine. Pin "engines": {"node":"20"} if needed.
Delete package-lock.json drift locally: rm -rf node_modules package-lock.json && npm install && git push.
For Docker apps, ensure Dockerfile has EXPOSE 3000 or whatever httpPort is set to — platform maps 204.168.174.49:PORT → container:EXPOSE and also injects PORT env.

2. App starts then crashes — `502 Proxy error` / `Health check failed`

Symptom: Blue-green log [BLUE-GREEN] New version failed its health check — rolled back, previous version kept online.

Your app must listen on process.env.PORT (not hard-coded 3000). Amemis injects PORT=3027 etc. and also rewrites .env PORT. Check server.js: const PORT = process.env.PORT || 3000.
Health check: default /health → /. Set a custom path in Settings → Health Check Path if needed; ensure it returns 2xx within 90 s.
Check Monitoring → Metrics — CPU/memory bars turn red at 80 % / 90 %. Bump cpuLimit / memoryLimitMb in Settings if hit.
View Monitoring → Logs filtered APP / ERROR with timestamps to see crash stack.

3. Auto-deploy not triggering on `git push`

Verify Deploy Apps → your app → Settings → Auto-deploy is ON (badge shows Auto-deploy ON).
Check branch matches push branch (e.g. VerboCalls-app vs master) — mismatched branch is ignored with event Push to "master" ignored — watching VerboCalls-app.
Ensure repo URL matches Settings → Repository (case-sensitive full_name). A push to a fork will be ignored.
Private repo: re-connect GitHub in Deploy → Connect a Git Provider or Monitoring → Settings → Git Providers — token may have expired. Reconciliation runs on boot but you can toggle Auto-deploy off/on to force re-register.
Need subscription: event Auto-deploy skipped — subscription required. Renew in Subscription.
Webhook URL: https://amemis.com/api/services/webhook/<id>/<secret> (visible in Monitoring → Settings → Webhook). Use Copy to re-add manually on GitHub Settings → Webhooks if deleted.

4. Git clone / webhook 403 — private repo or token

Event Invalid signature or Not found: webhook secret rotated — toggle Auto-deploy off/on.
GitLab/Bitbucket token expired: disconnect & re-connect provider; Amemis auto-refreshes 5 min before expiry via routes/git.js:113 ensureFreshToken.
Check Monitoring → Events timestamp — latest Git push webhook received (branch) from github should appear within seconds of push. If not, verify GitHub webhook Deliveries shows 200 (Amemis GitHub App) and that the branch is not behind by >50 commits (shallow clone depth 50 — force-push may need fresh clone).

5. 503 / 502 / Sleep — app is `stopped` or `asleep`

asleep is normal for Starter on idle (15 min). First request auto-wakes (Auto-waking service … in logs) or click Start in Deploy Apps. Set Always Awake (Premium) to disable.
stopped: click Start or Redeploy in Deploy Apps or Monitoring → Settings → Actions.
Check Monitoring → Metrics → Uptime and Running: true/false with internalPort — if port shows — the app never bound to PORT.

6. Database / env vars not loading

Env vars set in Dashboard take priority over .env file. Missing var? Check Monitoring → Settings → Environment Variables — add via + Add Variable → Save & Restart. Each save is logged with timestamp in Events.
DATABASE_URL / MONGODB_URI provisioned via database dropdown injects a container and auto-sets the connection string — ensure app reads the same key (see routes/deploy.js: databaseEnvKey).
Logs now show [ENV] Imported X variable(s) from .env file(s) (skipped platform keys: PORT,…) with date/time.

7. Logs & events — how to debug

Every line in Monitoring → Logs now is [YYYY-MM-DD HH:MM:SS] [LEVEL] [scope] message (from utils/telemetry.js). Use search + level filter (APP / ERROR / SYSTEM) — click Copy to share.
Every Monitoring → Events entry shows date: 2026-08-29 time: 13:19:22 dateTime: 2026-08-29 13:19:22 (from routes/events.js + models/deploy.js). Title + timestamp + data JSON if present.
Platform logs: GET /api/platform/logs?limit=200 and /api/platform/events also carry the same fields.
If you see repeated entry '.env' not uptodate, the Aug 29 fix already handles it — just push again. If it persists, click Redeploy to force a fresh clone.

Domain Limits

Starter plans include one custom domain per service. Premium plans include unlimited custom domains. Each custom domain must be a registered domain that you own.

Billing & Maintenance

Yearly Plans Include One Month Free

Paying yearly gives you 12 months of access for the price of 11 — that is, one month free. The full year is added to your subscription end date on the day the payment succeeds, and the plan renews yearly at the same rate unless you change or cancel it.

Starter: $9/month or $99/year (saves $9 — one month free).
Premium: $29/month or $319/year (saves $29 — one month free).
The free month is a discount on the yearly price, not an extra month added to your end date. A yearly payment never extends beyond 12 months of service.
Switching from yearly to monthly, or downgrading a plan, takes effect immediately and is not pro-rated — see Cancelling Does Not Produce a Refund below.

Cancelling Does Not Produce a Refund

Cancelling a subscription does not entitle you to a refund, a credit, or a pro-rated payout of any kind. Every amount you have already paid to Amemis is final and non-refundable — this includes yearly payments made with the one-month-free discount, and it includes the unused remainder of the billing period you paid for.

Specifically:

No refund on cancel. If you cancel a monthly or yearly plan, we do not refund the current or any previous billing period, and we do not return the unused days or months.
No refund for unused time. If you paid yearly and cancel after one month of using the service, the remaining eleven months are not refunded, credited, or carried over.
No pro-rating on upgrade or downgrade. Moving between plans, or between monthly and yearly billing, does not trigger a partial refund or a partial charge for the time already covered.
No refund for the one-month-free discount. The yearly discount is only available as a reduced yearly price; it is not a separate credit that can be withdrawn or claimed back.
No refund if we suspend for non-payment. If a renewal payment fails and the account is suspended, the outstanding balance must still be paid — suspension does not void the debt.
Domain, email and SSL purchases are also non-refundable once registered, provisioned, or issued, as set out in Payment Terms and Deployments Are Non-Refundable.
The only time money comes back is a duplicate or erroneous charge you report to us, which we reverse on the original payment method. Use Contact Us and we will look at it.

When Your Subscription Expires

Every plan is per service and has an end date. When that date passes and the subscription is not renewed, the app is disconnected. This applies to monthly and yearly plans identically — the only difference between them is how long the period lasts, not what happens at the end of it. Your code, repository link and settings are kept, so reconnecting is a payment rather than a rebuild.

If a subscription reaches its end date without being renewed, the app is stopped and stops serving traffic. It will not answer requests, and you will not be able to start it again until a plan is active. The 24-hour grace period below is the only buffer you get.

Monthly plans

End date: one month from the day you subscribed, then the same day each month after that.
Auto-renew ON: we charge your default saved card up to 2 days before the end date, so a healthy subscription renews before it ever lapses. Your end date then moves forward one month and the app is never disconnected.
Auto-renew OFF: nothing is charged. The end date passes, and 24 hours later the app is stopped and stops serving traffic.

Yearly plans

End date: one year from the day you subscribed — 12 months of access for the price of 11. The free month is a discount on the price, so a yearly plan never runs past 12 months.
Auto-renew ON: we charge your default saved card up to 2 days before the end date at the yearly rate, so the next 12 months are added and the app is never disconnected.
Auto-renew OFF: nothing is charged. The end date passes, and 24 hours later the app is stopped and stops serving traffic — even if eleven unused months remain, and even though you paid for twelve.
The one-month-free discount is not a renewal discount. Auto-renewing a yearly plan charges the full yearly price again; the free month applies once, on the yearly plan you buy.

How the grace period and auto-renew interact

The 24-hour grace period exists to absorb mistakes, not to give you free service. It covers clock skew and a payment that is still processing. It is not a head start on next month.
Auto-renew runs on a timer, not the instant your plan ends. We check for due renewals every few hours, so a renewal is normally collected within a day or two of it becoming due — well before the 24-hour stop.
If a renewal payment fails, we email you and the app is stopped 24 hours after the end date like any other lapsed plan. Fix the card and the app comes back.
Auto-renew needs a default saved card. With no card on file there is nothing to charge, so we turn auto-renew off and email you rather than letting the app lapse quietly.
A stopped app is brought back automatically if the renewal succeeds in time. If auto-renew is on, the card is valid and payment succeeds within 2 days after the end date, we restore the app by itself — you do not need to do anything, and the new period starts from the renewal date. Past that 2-day window auto-renew no longer applies, so renew from Dashboard → your app → Billing to reactivate. Your code and settings are kept either way; only a payment is needed.
Turning auto-renew off is final for that billing period. With the switch off we make no attempt to charge you, so the app is stopped 24 hours after the end date.
Domains, business email and SSL are separate purchases with their own end dates. Letting an app plan lapse does not cancel a domain you registered or expire a mailbox — and expiring one of those does not stop your app.

Check the end date and the auto-renew switch for each app under Dashboard → your app → Settings, and turn auto-renew on for anything you need to stay online.

Planned Maintenance

We do perform maintenance on Amemis from time to time, and occasionally the platform is briefly unavailable while we do it. Maintenance is how we ship new versions, apply security patches, upgrade the host, rebuild images, prune disk, and repair infrastructure — so it is a normal part of using the platform rather than an outage.

We aim to keep maintenance short and to do it outside peak hours. A typical platform update involves a brief restart of the platform process; user apps keep serving their existing build throughout and are only touched when the update is specifically about them.
Deploying a change to Amemis can mean a short maintenance window. Platform updates reach production through a controlled blue-green release — a new build is started and health-checked while the current version keeps serving traffic, then traffic is flipped over. If the new build fails its health check, the previous version stays live and the update is rolled back automatically, so a bad release does not become a maintenance incident for you.
Scheduled maintenance is announced in advance on the status page and, where the window is long or likely to be disruptive, by email to affected accounts. Unscheduled emergency maintenance is applied as soon as it is safe to do so, and we will say so afterwards.
Planned maintenance does not count against the uptime commitment in the Service Level section below, and no SLA credit is issued for it. Emergency maintenance that we are unable to avoid does count, in line with the SLA.
If maintenance runs past its announced window and your app is affected, check Monitoring → Logs / Events for the reason, then contact us — we will extend or credit the affected period as appropriate under the SLA.

Legal

Terms of Service

Acceptance

By accessing or using the Amemis platform, you agree to be bound by these Terms of Service. If you do not agree, do not use the service. These terms apply to all users, visitors, and anyone who accesses or uses the platform.

Account Terms

You are responsible for maintaining the security of your account credentials. You must provide accurate, current, and complete account information. You may not use the platform for any illegal or unauthorized purpose. You must notify us immediately of any unauthorized use of your account.

Acceptable Use

You agree not to misuse the Amemis platform or interfere with its operation. Prohibited activities include, but are not limited to: deploying malicious software, launching denial-of-service attacks, scraping or data mining without permission, hosting illegal content, and any activity that violates applicable law. We reserve the right to suspend any account that violates these terms.

Payment Terms

Paid plans are billed monthly or annually as selected. All fees are non-refundable. An annual payment buys 12 months of access for the price of 11 — one month free — and the free month is a discount on the annual price rather than extra service time, so an annual subscription never extends beyond 12 months. If you cancel your subscription, you will not receive a refund for any payments already made, including for partial billing periods and including the unused remainder of a yearly plan, and no pro-rated refund or credit is issued when you upgrade, downgrade, or move between monthly and yearly billing. See Cancelling Does Not Produce a Refund above. Auto-renewal payments are charged automatically at the start of each billing cycle until you cancel. We may change pricing with 30 days notice. If your payment fails, we may suspend access until the balance is paid. You are responsible for all taxes associated with your use of the service.

Deployments are non-refundable. A deployment, redeployment or auto-deploy cannot be cancelled or reversed once started, and no refund or credit is issued for a deployment — including one that fails, builds the wrong branch, or replaces a working app with broken code. Check your branch and configuration before you deploy. See Check Your Branch Before Deploying and Deployments Are Non-Refundable above.

Service Level

We strive to maintain 99.9% uptime for the platform. Our Service Level Agreement (SLA) provides credits if we fail to meet this commitment. Details are available on our SLA page. Announced and scheduled maintenance windows do not count against this commitment and no SLA credit is issued for them; emergency maintenance that we are unable to avoid does count, in line with the SLA. See Planned Maintenance above for how we deploy updates, how far ahead we announce them, and what happens if a window overruns. Amemis makes no guarantees about the availability of third-party services integrated with the platform.

Intellectual Property

You retain all rights to the code, content, and data you deploy on Amemis. The Amemis platform, including its proprietary software, brand, and design, is owned by Amemis, Inc. These terms do not grant you any license to our intellectual property beyond using the service as intended.

Termination

You may terminate your account at any time through the dashboard. We may terminate or suspend your account for violation of these terms, extended inactivity, or at our discretion with 30 days notice. Upon termination, you will not receive any refund for payments already made. Your services will be deactivated at the end of your current billing period. We will delete your data within 90 days unless required by law to retain it.

Expiry of a plan subscription is a termination of that service. Each service is billed separately and carries its own end date. If a monthly or yearly plan reaches its end date without being renewed — whether because auto-renew was off, the renewal payment failed, or no default card was on file — the app is stopped 24 hours after that date and stops serving traffic, and it cannot be started again until a plan is active again. Where auto-renew is on and collection succeeds, the end date is extended and the app is not stopped; a renewal that succeeds within 2 days after the end date also restores an app that has already been stopped. The unused remainder of the period is not refunded, credited, or carried over, and a yearly plan's one-month-free discount does not apply a second time on renewal. See When Your Subscription Expires above.

Limitation of Liability

Amemis, Inc. shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from your use of the platform. Our total liability is limited to the amount you paid us in the 12 months preceding the claim. Some jurisdictions do not allow certain limitations, so this may not apply to you.

Contact (Legal)

For questions about these terms, contact us at legal@amemis.com or write to Amemis, Inc., Attn: Legal Department.