New AIRLIFT Connect · shipping nowBuilt by cloudPWR · public-sector software since 2011SOC 2 Type II · GovRAMP member · WA OCIO approved

Available today · first shipping component of the new AIRLIFT

Stop moving government documents and data by hand.

AIRLIFT® Connect is the governed integration platform for public agencies — it captures completed forms, transforms the documents and data, and delivers them to the systems you already use, with role-based controls and an audit trail for every import.

Shipping
Today
Hosted in
Azure (US)
Built for
Agencies
Compliance
SOC 2 / HIPAA posture
AIRLIFT Connect configurator showing a pipeline: DocuSign source with two forms, Quillix INI transform, delivering to a Box folder destination and a Diagnostic destination.
Fig. 01 / configuratorDocuSign → Quillix INI → Box · Diagnostic
Status
Healthy
Last import
47s ago
Success · 24h
100%
§ 02 / The problemAgencies have tools — not pipelines.

Public agencies do not need another black-box integration.

Agencies already have digital tools — but too many critical handoffs still happen manually. Staff download signed PDFs, copy form values, rename files, upload packets, and search across multiple systems when something fails.

  • 01

    Manual handoffs survive every modernization push

    Completed forms still have to be downloaded, renamed, packaged, and uploaded — by hand, on someone's checklist.

  • 02

    Provider portals never share one operational view

    E-signature dashboards, file shares, content repositories, and downstream systems each tell a partial story.

  • 03

    Staff need answers without exposing sensitive records

    Troubleshooting cannot mean handing every operator access to credentials or system-level controls.

  • 04

    Traditional ECM is too large for the agencies that need it most

    Multi-year ECM replacements cost more and move slower than small and mid-sized agencies can carry.

§ 03 / How Connect workssource → transform → deliver → observe

From source event to delivered record — with every step visible.

AIRLIFT Connect works as a governed pipeline that links one source, optional transforms, and one or more destinations. Every import becomes a stage-by-stage ledger an operator can read.

  1. 01

    Capture

    Bring in completed e-signature forms, web service requests, and source events as normalized artifacts — documents, submitted form data, and mapped fields.

    • Adobe Acrobat Sign
    • Docusign
    • Web service
  2. 02

    Transform

    Normalize, map, package, or prepare documents and data for the receiving system. Transforms are explicit, declared, and auditable — not hidden inside a script.

    • Quillix INI packaging
    • Field mapping
    • Manifest assembly
  3. 03

    Deliver

    Send artifacts to Box, FTP, web services, or other configured destinations. Delivery failures are isolated and retryable — the rest of the pipeline does not stop.

    • Box folder delivery
    • FTP drop
    • Outbound web service
  4. 04

    Observe

    Track every import through queued, downloading, transforming, delivering, and completed states. Stop guessing where work stalled.

    • Import timeline
    • Stage history
    • Structured validation issues
§ 04 / Use casesOperator language, not connector language.

Common workflows Connect can automate.

§ 05 / IntegrationsExtensible by registry · not hardcoded.

Built to connect across providers — not lock workflow into one system.

AIRLIFT Connect integrates with e-signature platforms, content repositories, and downstream services through a registry-driven model, so new sources, transforms, and destinations can be added without rewriting the pipeline engine around any one vendor.

Sourcesevents in
  • Adobe Acrobat SignWeb Form
  • DocusignPowerForms · Web Forms
  • Web serviceAuthenticated inbound
Transformsreshape
  • Quillix INI packagingOrdered document set + manifest
  • Custom field mappingPipeline-scoped
  • More via extension modelRoadmap
Destinationsevents out
  • BoxFolder delivery
  • FTPStandard / SFTP drop
  • Web serviceOutbound delivery
§ 06 / Governance & securityPublic-sector controls, by design.

Automation with public-sector controls.

AIRLIFT Connect gives teams the visibility to support daily work while keeping sensitive controls, integration settings, and agency records available only to the right roles.

GovRAMP Member badge
GovRAMP member

cloudPWR is a GovRAMP member.

GovRAMP membership adds another public-sector trust marker alongside SOC 2 Type II certification, Washington State OCIO approval, and a HIPAA-oriented posture for regulated registry workloads.

Agency separation by design
Your agency's records, pipelines, and activity stay secure while work is running and while it is safely stored. Staff see the work they are responsible for — not unrelated customer records.
Role-appropriate access
Operational users can monitor imports and resolve issues without broad permission to change pipeline configuration, connection settings, or administrative controls.
Protected integration credentials
Sensitive connection details are kept behind managed controls, while support screens show the context and health information teams need to keep work moving.
Need-to-know work views
Operator screens are shaped around status, stage history, provider context, and next action, without exposing sensitive source details beyond what each role requires.
Integration health visibility
Teams can review provider connection state, setup guidance, and reconnect paths where the connected system supports them.
Readable operational timelines
Every import carries a stage history — queued, downloading, transforming, delivering, completed, partially failed, or failed — so teams can identify where work stopped without digging through raw logs.
Audit-ready configuration history
Pipeline configuration changes are kept traceable for review against the agency's records, approvals, and audit obligations.
Compliance posture
cloudPWR is a GovRAMP member, holds SOC 2 Type II certification, has Washington State OCIO approval, and maintains a HIPAA-oriented posture for regulated registry workloads.
§ 07 / The AIRLIFT suiteConnect is the first shipping piece.

The first shipping piece of AIRLIFT Next Generation.

Connect is available today. It provides the governed integration layer for the broader AIRLIFT product family now in development — Case Management, Content Management, Forms, Portal, and AIRLIFT Enterprise.

  1. 06AIRLIFT EnterpriseUnified composition of the family with shared identity, governance, workflow, content, and intelligence.In development
  2. 05AIRLIFT PortalCitizen- and staff-facing portal access across heterogeneous sources.In development
  3. 04AIRLIFT FormsElectronic form design, intelligent intake, and structured data extraction.In development
  4. 03AIRLIFT Case ManagementWorkflow automation, approvals, tasks, and reporting for agency case operations.In development
  5. 02AIRLIFT Content ManagementRecords and document management with pluggable storage backends, classification, and redaction.In development
  6. 01 AIRLIFT Connect Governed integration substrate. The foundation everything above will build on.Available now
§ 08 / CredibilityBuilt by a public-sector software team.

Built by a public-sector software team.

cloudPWR has served the public-sector software market since 2011. AIRLIFT products serve regulated registry workloads today — including the South Dakota Medical Cannabis Registry.

Read about cloudPWR
  • memberGovRAMP memberPublic-sector cloud community.
  • certSOC 2 Type IIIndependent control attestation.
  • govWA OCIO approvedWashington State Office of the CIO.
  • hipaaHIPAA postureFor regulated registry workloads.
Partners · providers · procurement06 / curated
  1. 01AccelaGovtech LOB platform
  2. 02Adobe Acrobat SignE-signature platform
  3. 03DocusignE-signature platform
  4. 04BoxContent & document storage
  5. 05CarahsoftPublic-sector distributor
  6. 06NASPOPublic-sector purchasing path
§ 09 / FAQAnswers for agencies evaluating Connect.

Frequently asked questions.

Straight answers about what AIRLIFT Connect is, where it comes from, and how cloudPWR governs public-sector documents and data.

What is AIRLIFT Connect?
AIRLIFT Connect is a governed integration platform for public agencies, built by cloudPWR. It captures completed forms and source events, transforms the documents and data, and delivers them to the systems an agency already uses — with role-based controls and an audit-ready timeline for every import. It is the next generation of cloudPWR's Connect — now shipping as the first component of the broader AIRLIFT suite.
Is AIRLIFT Connect a brand-new product?
AIRLIFT Connect is the next generation of cloudPWR's Connect — a ground-up rebuild, not an untested new tool. cloudPWR has delivered integration and content software to public-sector agencies since 2011, and Connect carries that operational experience into a modern, governed platform. The technology is new; the track record behind it is not.
Who is AIRLIFT built for?
AIRLIFT is built for state and local government agencies that need to move documents and data between the tools they already use without manual handoffs. It is designed around public-sector controls — agency data separation, role-appropriate access, and audit-ready history — so regulated teams can automate work while keeping sensitive records restricted to the right roles.
How does AIRLIFT Connect work?
AIRLIFT Connect works as a governed pipeline with four stages: capture, transform, deliver, and observe. It brings in completed e-signature forms and authenticated web service events, normalizes or packages the documents and data, delivers them to destinations such as Box, FTP/SFTP, or outbound web services, and records every import as a readable, stage-by-stage timeline.
What systems does AIRLIFT Connect integrate with?
AIRLIFT Connect captures from Adobe Acrobat Sign, Docusign, and authenticated inbound web services; transforms data with Quillix INI packaging and custom field mapping; and delivers to Box, FTP/SFTP, and outbound web services. A registry-driven model lets new sources, transforms, and destinations be added without rewriting the pipeline engine around any one vendor, so integration availability can expand by deployment.
Does AIRLIFT support HIPAA-regulated workflows?
Yes. AIRLIFT supports HIPAA-regulated workflows, and cloudPWR signs Business Associate Agreements (BAAs) — with active BAAs in place with agency customers today. Governance controls such as agency data separation, role-appropriate access, protected integration credentials, and audit-ready configuration history support the handling of protected health information.
What are AIRLIFT's security and compliance certifications?
cloudPWR, the maker of AIRLIFT, is a GovRAMP member, holds SOC 2 Type II certification, and has Washington State OCIO approval, alongside a HIPAA-oriented posture for regulated registry workloads. GovRAMP is the state and local government counterpart to the federal FedRAMP program.
Where is AIRLIFT hosted?
AIRLIFT is hosted on Microsoft Azure in the United States. Running on Azure's US regions supports the data-residency and security expectations of public-sector agencies.
How is AIRLIFT Connect different from a generic integration platform?
Unlike a general-purpose integration or iPaaS tool, AIRLIFT Connect is built specifically for public-sector governance. Transforms are explicit, declared, and auditable rather than hidden in scripts; operators get role-appropriate visibility without access to credentials or configuration; and every import carries an audit-ready timeline. It is designed for agencies that must answer to auditors, not only move data.
What is the relationship between AIRLIFT and cloudPWR?
AIRLIFT is a product line built by cloudPWR, a public-sector software company founded in 2011 and based in Post Falls, Idaho. AIRLIFT Connect is the first shipping AIRLIFT component; the broader suite — Case Management, Content Management, Forms, Portal, and AIRLIFT Enterprise — is in development.
§ 10 / Talk to cloudPWR

See where governed integration can remove manual work in your agency.

Schedule a working demo with the cloudPWR team. We'll walk a real pipeline — source, transform, destination, observe — against a workflow your agency runs today.

  • Response timeOne business day
  • Demo length30–45 min
  • BringOne workflow you'd like to govern