- Starting price
- Compute from $0.03/hour
- Free tier
- No
- Platforms
- Web console · REST API · Terraform · TypeScript, Go, and Python SDKs · MCP
- Developer
- American Cloud, LLC
- Launched
- 2022
- Updated
- Aug 9, 2026
The verdict
American Cloud is a credible smaller-cloud option, not merely “Christian hosting” with a reseller control panel. Standard VMs, managed Kubernetes, PostgreSQL/MySQL/Redis, S3-compatible storage, Terraform, SDKs and zero egress pricing can materially simplify a ministry’s infrastructure bill and exit plan. Its values-based anti-deplatforming posture is still a commercial promise governed by an acceptable-use policy, suspension rights and a services agreement. That agreement also makes the customer responsible for backups, offers only seven days to copy data after termination and contains extraordinarily broad monitoring and disclosure consent. Compare a real workload, negotiate those terms where stakes are high and maintain an independent restore path.
Try American Cloud ↗Opens americancloud.com
American Cloud is a US infrastructure provider founded by Army veteran and cloud-industry operator Aron Wagner. It positions itself as an independent alternative to AWS, Google Cloud and Microsoft Azure for customers who want domestic infrastructure, predictable pricing, open standards and less risk that a broad platform policy change will disrupt a lawful organization. The current catalog includes virtual machines, virtual private clouds, managed Kubernetes, managed PostgreSQL/MySQL/Redis, block and object storage, DNS, load balancing, autoscaling, managed WordPress and physical colocation.
This is real infrastructure rather than a values badge attached to another hyperscaler. Compute offers all-SSD or NVMe storage, snapshots, metrics, SSH and a browser console. Kubernetes exposes standard kubectl and API access with single-node or high-availability control planes and no separate control-plane fee. Databases use standard engines and connection strings. Object storage is S3-compatible at $0.02 per GB per month, starts at 250 GB, permits up to 1,000 buckets and advertises no request or egress charges. The company also operates an OpenColo facility in Santa Clara and describes a second cloud region completed in 2025.
Developer tooling improved substantially in 2026. The portal and REST API are joined by official TypeScript, Go and Python SDKs, a Terraform provider and an open-source Model Context Protocol server. The MCP integration supports conversational infrastructure operations and is read-only by default, an important safety choice, while the same typed API underpins code and infrastructure-as-code workflows. Open-source components publicly identified by American Cloud include Apache CloudStack, PowerDNS, KubeBlocks and Ceph. Portability is not automatic, but standard engines, S3 semantics, Kubernetes and Terraform reduce proprietary surface area.
The website says compute starts at $0.03 an hour and promotes flat monthly pricing with no network ingress or egress charge. A dynamic calculator covers compute, Kubernetes, databases, block storage, VPC, object storage, load balancing and WordPress, but its public text does not preserve a stable price table for every combination. Quotes are therefore workload-specific. A small VM running continuously at the headline floor would be about $21.90 in a 730-hour month before storage or add-ons. Object storage has a 250 GB starting allocation, making its practical floor about $5 monthly at the printed per-GB rate.
American Cloud’s legal pages matter as much as its calculator. The Services Agreement identifies American Cloud, LLC, a Delaware LLC with a Pennsylvania registered address; the privacy page calls the entity American Cloud Inc., an inconsistency that should be corrected. The 2022 SLA “seeks” 99.9% network uptime and pays service credit only for qualified, documented downtime. The customer must report an incident within 24 hours. This researched review examined official product, pricing, legal, privacy, SLA and developer materials. We did not deploy a server, benchmark compute or storage, test support, review a SOC report, verify data-center architecture, simulate failover or conduct a security assessment.
✓ The good
- No egress-fee model - predictable outbound transfer can remove one of the largest barriers to cloud exit and media delivery
- Open-standard products - Kubernetes, PostgreSQL, MySQL, Redis and S3-compatible APIs reduce proprietary application changes
- Transparent entry pricing - compute starts at $0.03/hour and object storage is printed at $0.02/GB/month
- Strong developer surface - dashboard, REST API, Terraform, three official SDKs and a read-only-default MCP server
- Managed and self-directed options - organizations can combine VMs, databases, orchestration, WordPress and physical colocation
- Human support positioning - product pages promise round-the-clock access to English-speaking infrastructure engineers
- Narrower acceptable-use list - the public AUP names concrete unlawful and harmful categories instead of vague viewpoint tests
- Portable exit ingredients - standard dump tools, S3 clients, VM image import and ordinary Kubernetes manifests support migration
✗ Watch out
- Broad monitoring consent - the contract authorizes unrestricted monitoring, recording, searching and disclosure of system data
- Customer owns backup risk - unless an order says otherwise, maintenance, integrity, retention, disaster recovery and backup are yours
- Only seven days after termination - eligible customers receive a short window to copy data before it may be deleted
- Modest SLA - 99.9% allows about 43.8 minutes of monthly downtime before exclusions and is measured internally
- Credit procedure is strict - incidents need documentation within 24 hours and only full 30-minute blocks earn 5%
- Legal pages are old - most controlling policies date to October 2022 despite major 2025–2026 product expansion
- No stable full price table - the client-side calculator makes longitudinal and apples-to-apples comparison harder
- Smaller ecosystem and footprint - services, regions, partner depth and third-party expertise are narrower than hyperscalers
Best for
- US churches, ministries and values-conscious businesses seeking an independent infrastructure provider
- Teams with high outbound-transfer costs that can verify the no-egress policy for their exact architecture
- Standard Linux, Kubernetes, PostgreSQL, MySQL, Redis and S3-compatible workloads
- Organizations prepared to maintain off-provider backups and rehearse restoration elsewhere
- Developers who value Terraform and API portability more than a huge proprietary managed-service catalog
Avoid if
- You need dozens of regions, specialized AI/analytics services or a vast certified partner ecosystem
- Your security or privacy program cannot accept the contract’s unrestricted monitoring and disclosure language
- You expect the provider to own backup, disaster recovery and continuity without a written order
- A 99.9% network SLA or short claim window is inadequate for your service commitments
- You are choosing purely because of anti-deplatforming language without testing cost, reliability and exit
What American Cloud is
American Cloud is an infrastructure provider, not a church website builder or turnkey ministry app. A technical team remains responsible for operating the application, protecting credentials, configuring firewalls, patching workloads outside managed scope, controlling cost, backing up data and meeting every legal obligation to users. Marketplace images accelerate deployment but do not transfer application security to the provider.
Its religious relevance is institutional rather than devotional. Faith.tools lists it because organizations worried about viewpoint-based deplatforming may prefer a provider whose published philosophy favors lawful speech and narrow intervention. The official AUP still prohibits incitement, infringement, defamation, trafficking, illegal goods, intentionally harmful privacy violations, malware, doxing, phishing and spam. No cloud can promise service regardless of law, payment, abuse, operational risk or court order.
Why independence and “anti-lock-in” need a technical exit test
American ownership, no egress charge and a narrower content policy address genuine organizational risks. A ministry migrating terabytes of video can avoid a punitive final transfer bill; standard database engines and S3-compatible clients can reduce rewriting; and a smaller operator may offer direct engineering support. Those benefits are more measurable than a cultural slogan. Price a representative month, transfer data out, open a support incident and restore a copy on a second provider during evaluation.
The contract remains the boundary. American Cloud can suspend for uncured breach, immediate operational or security risk and legal order; data violating the AUP may be deleted; and a customer ending a longer service period can owe remaining fees. “Cancel-proof” should never be interpreted literally. Genuine resilience is multi-layered: portable formats, DNS control, source and infrastructure code, off-provider backups, documented dependencies, recovery credentials and a rehearsed move. A friendlier provider can lower the probability of disruption but cannot eliminate concentration risk.
Compute, networks and storage: a useful core with customer-owned operations
Virtual machines offer selectable location, OS, server size, SSH keys, elastic or VPC networking, subnets, ACLs, firewall rules, NAT, port forwarding, attached SSD volumes, real-time metrics, snapshots and browser console access. Marketplace images include WordPress, GitLab, Supabase and Coolify. Object storage exposes S3-compatible commands, access keys, bucket and per-object controls, pre-signed URLs and common tools such as AWS CLI, s3cmd and rclone.
A snapshot is not a backup strategy until it survives account compromise and provider loss. Export databases and objects to a separate failure domain, encrypt them with customer-controlled keys where appropriate and test full restoration. Restrict web-console and API privileges, rotate access keys, separate billing from production administration and alert on unexpected resource creation. The Services Agreement assigns the customer responsibility for data integrity, retention, continuity, disaster recovery and backup unless an order explicitly changes it.
Managed Kubernetes and databases: portability without parity
Kubernetes supports standard kubectl, manifests, Helm, NGINX or Istio ingress, attached persistent volumes, autoscaling, multiple versions and either a single control node for development or multi-master HA for production. Managed databases cover PostgreSQL, MySQL and Redis with standard connections, isolated networking, configurable compute/storage, scheduled backup, point-in-time recovery, scaling and a production HA tier. The product avoids a control-plane fee and proprietary database API.
Standard interfaces reduce migration work but do not make services identical. Verify supported database versions and extensions, maintenance windows, restore granularity, replication, connection limits, Kubernetes upgrade policy, CSI behavior, load balancer semantics, network egress paths and observability integration. Export with pg_dump, mysqldump or Redis formats and restore outside the platform. A standard API is the beginning of portability; compatible data, automation and operating knowledge complete it.
Terraform, SDKs, API and MCP: automation deserves constrained credentials
Official SDKs for TypeScript, Go and Python, the Terraform provider and REST API bring the platform beyond manual portal administration. Infrastructure can be reviewed in code and recreated consistently. The MCP server connects supported AI clients to more natural-language cloud operations and uses read-only behavior by default, according to the product site. That default makes exploration, inventory and troubleshooting safer than beginning with delete-capable credentials.
Keep read-only MCP read-only in production unless a narrow, reversible task justifies otherwise. Treat model output as an untrusted proposal, review the exact API call and never expose root or billing credentials to a chat context. Pin provider and SDK versions, run Terraform plans through review, store state securely and protect import/destruction operations. Automation reduces drift only when changes are attributable, reproducible and recoverable; it can accelerate an outage when credentials and approvals are broad.
Pricing
Cloud compute
From $0.03/hour
Virtual machines are configured by vCPU, memory, root storage, network and billing cycle. The headline floor equals about $21.90 over 730 hours, but the public calculator—not that multiplication—controls the selected configuration. Include block storage, snapshots, IPs, load balancing, tax and support scope in a production estimate.
A2 object storage
$0.02/GB/month; 250 GB minimum
S3-compatible storage advertises no ingress, egress or API-request fees, with a 250 GB starting allocation, up to 1,000 buckets, per-file permissions, pre-signed URLs and common S3 client support. At the printed rate, the starting allocation is roughly $5 monthly. Confirm replication, durability, versioning and retrieval behavior.
Managed platform services
Calculator / configuration based
Kubernetes has no separate control-plane fee, while worker nodes and storage remain billable. Managed PostgreSQL, MySQL and Redis offer dev and HA production tiers. VPC, block storage, load balancing, DNS, autoscaling and WordPress add their own resources. Save the quote because no static all-SKU rate card is published.
Colocation and enterprise
Custom quote
OpenColo racks, cages, power, cross-connects, migration help, custom support and enterprise configurations require direct scoping. The facility page advertises month-to-month arrangements, but any longer service period in an order can make the remaining fees immediately due on early customer termination.
Zero ingress and egress fees are the pricing headline. They are most valuable for media, backups, public downloads and migrations where hyperscaler transfer charges dominate the compute line.
Compute begins at $0.03 an hour, while object storage prints $0.02 per GB monthly with a 250 GB minimum and no request charge. Managed and network services should be modeled through the calculator.
The agreement says all fees are nonrefundable and third-party cost changes can flow through with notice. Usage-based services round consumed units up and the customer is responsible for monitoring usage.
Compare a complete workload, not one VM. Include HA replicas, volumes, snapshots, load balancers, IPs, DNS, monitoring, support, off-site backup, staff time and the cost of meeting your own uptime commitment.
Where American Cloud falls behind
The Services Agreement’s monitoring clause is exceptionally broad. It says all communications and data transiting or stored on the information system will be monitored and grants consent to unrestricted interception, recording, searching and disclosure at any time and for any purpose to American Cloud and authorized parties, including government entities. That wording conflicts with the ordinary expectation of confidential hosted content and deserves negotiation or legal review.
“Anti-lock-in” marketing sits beside a seven-day exit window. After an eligible termination, a paid and compliant customer may copy data for seven days; after that American Cloud has no retention obligation and may delete without liability. The contract promises no transition help unless separately written. An operational exit must therefore begin before termination.
The published 99.9% network SLA is modest and heavily qualified. Downtime excludes scheduled/emergency maintenance, external connectivity, third-party hardware or software, customer actions, force majeure and other categories. The company measures with its internal systems, requires detailed notice within 24 hours, counts only entire 30-minute blocks and makes credits the sole remedy.
Marketing references stronger data-center characteristics, but a colocation facility figure should not be confused with the cloud-service commitment. Buyers need the exact SLA, availability architecture, region and managed service in their order. A multi-zone design cannot be inferred from “American infrastructure.”
The legal corpus has not kept pace visibly with the product. The privacy policy, agreement, AUP, GDPR notice and SLA are dated October 17, 2022, while managed databases, expanded regions, MCP and SDKs evolved through 2025–2026. The privacy page also names American Cloud Inc. while the agreement names American Cloud, LLC. Current subprocessors, telemetry, product-specific retention and account security should be documented.
There is no permanent free tier for meaningful deployment and no simple trial commitment printed on the public price page. That is normal for infrastructure, but it means evaluation can generate charges immediately. Use budgets and alerts, remove resources after testing and confirm whether stopped compute, reserved storage, snapshots, IPs and control planes continue billing.
The provider’s smaller footprint limits region diversity and specialized services. Teams deeply dependent on serverless functions, proprietary analytics, AI platforms, global edge products or mature marketplace integrations will need replacements or a hybrid architecture. Simplicity is valuable only if the catalog covers the workload.
American Cloud vs. AWS vs. DigitalOcean
AWS has unmatched regions, services, compliance programs and expertise, but its product and cost complexity can overwhelm a small ministry. American Cloud offers a tighter catalog, direct support, standard infrastructure and no egress fee. Choose AWS when specialized managed capability or global redundancy justifies the governance burden; choose American Cloud when ordinary compute, storage, Kubernetes and databases cover the need and a verified exit matters more.
DigitalOcean is the closer usability competitor: straightforward VMs, managed Kubernetes, databases, object storage, application services and a large developer library. It has broader market adoption and established public documentation. American Cloud differentiates through US independence, values-oriented policy, zero egress positioning and colocation continuity. Compare identical servers, transfer, support, region, database and SLA—not category slogans.
A church-specific host may manage WordPress and ministry integrations for nontechnical staff, while American Cloud still expects infrastructure competence outside any managed scope. Conversely, self-hosting hardware creates power, connectivity, patching and recovery burdens that a cloud absorbs. The right choice is the smallest operational model the team can secure and restore, with no critical data trapped behind one account.
The bottom line
American Cloud deserves consideration because it has built a coherent independent cloud stack, current developer tooling and a price model that attacks real egress and lock-in pain. Its strongest case is technical: standard engines and APIs, no transfer charge, human support and a feasible migration path. Its weakest case is contractual. The 2022 agreement shifts backup and continuity to the customer, gives only seven days for post-termination copying, limits availability remedies and includes sweeping monitoring consent. Do not buy a cloud on affinity alone. Deploy a representative noncritical workload, compare its full cost and latency, test support, export every data class, restore somewhere else and have qualified reviewers examine the order, SLA, monitoring language and DPA. If those checks pass, American Cloud can be a valuable part of a resilient ministry infrastructure strategy.
Alternatives to American Cloud
Frequently asked questions
What is American Cloud?
American Cloud is an independent US infrastructure provider offering virtual machines, networking, managed Kubernetes, PostgreSQL/MySQL/Redis, block and S3-compatible object storage, DNS, load balancing, autoscaling, managed WordPress and colocation. Developers can use a web console, REST API, Terraform, TypeScript/Go/Python SDKs and an MCP server. It is infrastructure, not a turnkey Bible or church-management app.
How much does American Cloud cost?
The official compute page says virtual machines start at $0.03 per hour—about $21.90 for 730 continuous hours at the exact floor before other resources. Object storage is $0.02 per GB monthly, starts at 250 GB and advertises no request or egress fee. Kubernetes, databases, volumes, networking, load balancing and WordPress are configuration priced through the calculator. There is no permanent free deployment tier stated.
Does American Cloud really have no egress fees?
Its current pricing and product pages say there are no ingress or egress fees, and object storage also says API requests are free. Confirm the rule for the exact service, region, private/inter-region traffic, abuse thresholds and any third-party network product in your order. Transfer a representative dataset during evaluation and retain the written plan because website pricing can change.
Can American Cloud guarantee that my organization will never be deplatformed?
No provider can. American Cloud publishes a narrower acceptable-use policy and contract language treating suspension as serious, but it can suspend for material breach, nonpayment, operational or security risk and court orders, and can remove AUP-violating data. Its values may reduce one risk; contractual compliance, legal orders, infrastructure failure and business concentration remain. Maintain DNS control, portable automation and tested off-provider backups.
What uptime does American Cloud guarantee?
The published 2022 SLA says American Cloud “seeks” 99.9% network uptime measured by its internal systems. Qualified downtime earns 5% of the affected service fee for each full 30 minutes, subject to exclusions. The customer must submit detailed documentation within 24 hours, credits can take two billing cycles and are the sole remedy. Negotiate stronger terms if your own customer promise exceeds that commitment.
Who is responsible for backups and disaster recovery?
The Services Agreement assigns data maintenance, integrity, retention, security, business continuity, disaster recovery and backup to the customer unless a specific order says otherwise. Snapshots and managed database backups are useful features, not an independent recovery plan. Keep encrypted copies in another provider or offline location, record restoration steps and test them on a schedule.
What should a church check before moving to American Cloud?
Price a complete workload; confirm region, subprocessor, security and compliance evidence; review the monitoring consent and DPA; test support, alerts, role access and MFA; document every billable resource; export databases, objects, secrets, images, DNS and infrastructure code; and restore them elsewhere. Ensure the church—not a contractor alone—controls the domain, billing, source repository, backup keys and emergency contacts.
Sources & further reading
More Focus, Habit & Productivity Apps
EpistleEpistle brings missionary updates, partner responses and ministry-partner-development records into one thoughtful workflow—powerful for ordinary communication, but sensitive stories, donor data and AI coaching demand much clearer boundaries than a newsletter tool alone.
The GAPPThe GAPP gives mission teams a configurable system for recording activity, groups, churches and people-group context across offline fieldwork—capable operational software whose location-rich spiritual records require a threat model before a rollout.
Disciple.ToolsDisciple.Tools is a free open-source CRM for contacts, groups, churches, coaching and movement maps that organizations can control on their own WordPress infrastructure—an unusually capable system whose freedom transfers security and governance to the operator.
GlossaGlossa sends live sermon captions and translated audio in more than 100 languages to ordinary phones, with church-specific vocabulary and optional voice cloning—but leaders must test accuracy, consent, latency, privacy and fallback plans before Sunday dependence.
AtomsAtoms turns James Clear’s Atomic Habits framework into reminders, repetitions, identity cues, lessons, and progress tracking—an elegant aid for consistent practices, but a religiously neutral tracker whose privacy disclosures and cross-platform quality need scrutiny.
Hope TranslatorLive captions and AI translation let listeners follow a sermon from any phone without installing an app—but pricing is complex and the privacy policy never explains microphone or transcript handling.