Skip to main content

HIPAA Compliant Flight PHP Hosting

We run Flight PHP services for healthcare teams on a single-tenant AWS environment, with the Business Associate Agreement signed within 24 hours on managed tiers. Managed tiers from $199/mo.

See tiers and pricing Request a quote

How your service fits together

Account for the small service nobody remembers owning

Who can reach this endpoint, and which systems does it pass data to?

1

Internal users, devices or callbacks

Your users, application choices and external services determine what needs to connect.

Inside your dedicated hosting environment

2

Your Flight PHP service

Confirm application maintenance, access and deployment responsibilities during scoping.

3

Whatever the service stores or forwards

Hosting includes encryption, audit logging and tested backups. Plan capacity follows your workload.

Illustrative operating model. Your final architecture and responsibilities are agreed during scoping. Connected applications and services need their own review; a hosting agreement does not establish their suitability.
Discuss your Flight PHP architecture

Why Flight PHP needs a HIPAA host, not a generic one

Flight is for small, fast endpoints: internal tools, device callbacks, glue services. The risk with small services is not complexity, it is that they get forgotten.

The service nobody remembers owning

Small internal endpoints are stood up quickly and reviewed rarely. Running one on monitored, patched, single-tenant infrastructure means that being forgotten is much less dangerous than it would otherwise be.

Internal is not the same as private

A tool only staff use still handles patient data and still needs a Business Associate Agreement behind it. Internal audiences change the threat model; they do not change what the law asks of you.

Minimal application, full platform

A few hundred lines of routing sits on the same hardened baseline as everything else: isolated account, encryption, WAF, audit logging, backups and monitoring configured before handover.

Where our responsibility ends

Stated plainly, because knowing this before an incident is worth more than discovering it during one.

We run

  • The AWS account, VPC and network isolation
  • The operating system, patching and hardening
  • PHP, the web server, the database and TLS
  • CloudFront, the WAF, encryption, audit logging and backups
  • Monitoring and infrastructure incident response

You run

  • Your Flight application and its routes
  • Framework and dependency updates, unless scoped with us
  • Who can reach the service and how it authenticates them
  • The systems it talks to and the data it passes on

If a problem turns out to be the server, PHP or the infrastructure, open a ticket and we take it. If it is inside your service, we tell you what we found and hand it back with recommendations.

HIPAA hosting vs standard hosting

A $10 shared plan is not slightly less compliant; it is categorically different. Most mainstream hosts will not sign a BAA for shared hosting at any price.

Signed BAA before any PHI arrives
Standard Hosting
Not included
HIPAA Compliant
Included
Single-tenant isolation
Standard Hosting
Not included
HIPAA Compliant
Included
Encryption on by default, at rest and in transit
Standard Hosting
Not included
HIPAA Compliant
Included
Audit logs centralized and kept six years
Standard Hosting
Not included
HIPAA Compliant
Included
Encrypted backups with tested restores
Standard Hosting
Not included
HIPAA Compliant
Included
Written responsibility split
Standard Hosting
Not included
HIPAA Compliant
Included

Flight PHP hosting tiers

Every tier is a single-tenant AWS account with a signed BAA and the same compliance baseline. What changes is capacity.

Help me choose a hosting tier

Choose capacity for your workload, rather than the size of your organization. The published tiers share the compliance baseline described above.

CPU and memory
Consider concurrent requests, background jobs, database work and your application's memory needs. Traffic alone does not tell the whole story.
Storage and backups
Allow room for your application, database, uploads and expected growth. Compare the listed live-storage and backup allocations separately.
Data transfer
Estimate outgoing data from page visits, downloads and integrations, then compare it with the included transfer.
When to size up or scope a custom setup
Review capacity when monitoring shows sustained resource pressure or you expect a workload increase. Availability and recovery goals may require architecture changes, not simply a larger server.

Unsure where to start? Share the requirements you know. An engineer can help you choose an existing tier or scope a custom configuration.

Discuss Flight PHP capacity with an engineer

  • Starter

    $199/mo

    or $2,269/yr

    Compute
    1 vCPU
    Memory
    2 GB
    Storage
    50 GB
    Backups
    100 GB
    Transfer
    250 GB
    Order Starter

  • Solo

    $349/mo

    or $3,979/yr

    Compute
    2 vCPU
    Memory
    4 GB
    Storage
    100 GB
    Backups
    200 GB
    Transfer
    500 GB
    Order Solo

  • Practice

    $499/mo

    or $5,689/yr

    Compute
    4 vCPU
    Memory
    8 GB
    Storage
    200 GB
    Backups
    400 GB
    Transfer
    1,000 GB
    Order Practice

  • Clinic

    $849/mo

    or $9,679/yr

    Compute
    8 vCPU
    Memory
    16 GB
    Storage
    400 GB
    Backups
    800 GB
    Transfer
    2,000 GB
    Order Clinic

  • Group

    $1,499/mo

    or $17,089/yr

    Compute
    16 vCPU
    Memory
    32 GB
    Storage
    600 GB
    Backups
    1200 GB
    Transfer
    3,000 GB
    Order Group

  • Network

    $2,799/mo

    or $31,909/yr

    Compute
    32 vCPU
    Memory
    64 GB
    Storage
    800 GB
    Backups
    1600 GB
    Transfer
    5,000 GB
    Order Network

What every Flight PHP tier includes

The same compliance baseline at Solo and at Network. Capacity is the only thing that changes.

  • Single-tenant AWS environment
  • CloudFront CDN in front of every tier
  • Web application firewall
  • EBS storage with 7-day snapshot retention
  • Encryption at rest and in transit
  • Six-year audit logging
  • Tested, encrypted backups
  • Migration included
  • BAA signed within 24 hours of signup
  • 24/7 team, monitoring and infrastructure incident response

Know who owns the next step

Clear scope matters before launch and when you need help.

Hosting operations

Our published managed-hosting baseline includes 24/7 monitoring and infrastructure incident response, patching, logging and tested backups. Application changes and third-party integrations depend on the agreed scope.

Customer support route

Before you commit

Review the BAA, responsibility split, backup and recovery requirements, migration steps and support contacts with us. Tell us which procurement documents your organization needs so we can confirm what is available.

Review scope and documentation

Planning a new service

Quotes and general inquiries use our contact process during business hours. Existing customers should use their account's support instructions for infrastructure incidents.

Contact the team

Flight PHP hosting questions

Is a micro-framework appropriate for healthcare work?
For a narrow job, often yes. Less framework means less to keep patched. What it does not reduce is the hosting obligation: the same isolation, encryption, logging, backups and Business Associate Agreement apply to a hundred-line service and a hundred-thousand-line one alike.
This is only used internally. Does that change anything?
Not from a HIPAA perspective. If the service touches protected health information, the safeguards and the agreement are required regardless of who the users are. Internal-only usually means fewer attackers, not fewer obligations.
Can we run several small services?
Yes, and the sensible shape depends on how they relate to each other. Capacity is what separates the tiers, so several small services often fit comfortably within one. That is worth a conversation rather than a guess.

Find the right Flight PHP setup

Tell us what you run, what you need to move and who manages the application. We will help you scope capacity and responsibilities before you choose a tier.

Discuss your Flight PHP workload Compare tiers