Frequently asked questions

Start with the problem you are trying to solve—forms, events, or a very specific internal workflow. HIPAA-compliant forms are ideal for collecting protected health information, Event Maker is for registrations and ticketing, Rubric is for structured scoring, and Custom Apps are better when none of the above quite fits.

Yes. Most Apps can integrate with common CRMs, marketing tools, and back-office systems using webhooks, APIs, or lightweight middleware. During onboarding we’ll review your stack and outline what’s possible and what requires custom work.

Yes. For many customers we start with an existing app such as HIPAA-compliant forms or Event Maker and then layer on custom workflows, fields, or integrations so it matches how your team actually works.

Apps are designed to work well for very small teams but still support growth—adding new users, roles, and environments as you scale. We can discuss where you are today and where you expect to be in 12–24 months.

We start with a short discovery call, then map your workflows, configure a test environment, and walk you through a pilot. Once everything looks good, we agree on a go-live plan, training, and basic documentation.

Bugs and feature requests are tracked in a shared queue. We prioritize issues that affect stability or compliance first, then work through quality-of-life improvements. Larger feature requests are estimated and scheduled with you.

Web Support usually includes updates, troubleshooting, performance tuning, security hardening, and help with deployments for WordPress, Next.js, and Joomla sites. We also help with DNS, SSL, email routing, and control panels when they affect your site.

Most non-urgent tickets get an initial response within business hours, and priority plans include faster response times plus a clearer escalation path for outages. For critical incidents we work with you to define severity levels and who gets notified.

Yes. A lot of our work is supporting or stabilizing sites built by other agencies or freelancers. We start with a brief assessment so we understand the stack, then create a short plan for updates, fixes, and monitoring.

We support both. Many customers start with a one-off incident or small project and then move to a recurring plan once they see the value of having someone on call who already knows their environment.

Yes. We often work alongside in-house IT, marketing, or external agencies. We clarify who owns which systems, then document a simple communication path so issues do not fall between teams.

Typically we need access to your hosting panel, code repository (if you have one), and any third-party services that affect the site—such as DNS, SSL provider, or email delivery. We document this during onboarding so future work is fast and predictable.

CloudAxe hosting focuses on a clean, well-understood stack with monitoring, backups, and restore testing built in. We optimize for small business sites that need reliability and clear communication, not experimental infrastructure.

Backups are taken on a schedule and stored off-server, and we periodically perform restore tests so we know they work in practice, not just in theory. If you ever need a restore, we already have a tested path to bring your site back online.

Yes. We handle the full migration plan—cloning the site, syncing databases and files, handling DNS and SSL, and scheduling the final cutover. The aim is to minimize downtime and avoid surprises during the switch.

Yes. For most sites we recommend a staging environment where we can safely test updates, new features, and configuration changes before they reach production.

We use monitoring that checks uptime, key health indicators, and basic performance. When something looks off, we investigate and either handle it directly or coordinate with you, depending on your plan.

If you are on a managed hosting plan, we look at scaling options, caching, and CDN configuration to keep the site stable. We also review what caused the spike so we can right-size the environment going forward.