Highlights
Introducing Incode Know Your Agent Introducing TrustGraph Introducing GovFaceMatch 3 years in a row named a Leader
01/04
01/04
Back to blog
An illustration of a magnifying glass above the FedRAMP logo

What FedRAMP In Process status means for federal identity verification

The FedRAMP authorization process can take time. So how can agencies gauge when a specific solution will be available to them?

Agencies are being asked to move faster, prioritize commercial-first solutions, and modernize citizen services, all while stopping synthetic identities and deepfakes without adding risk. That direction is explicit: Executive Order 14275 calls for “expedited and streamlined acquisitions,” while OMB’s M-26-12 reinforces the requirement to procure commercially available products and services “to the maximum extent practicable.” A cloud vendor that stalls halfway through authorization delays an agency’s ability to meet those goals.

Cloud service providers (CSPs) need to make FedRAMP authorization a priority, be transparent about their progress, and deliver on their commitments. That’s why I want to be clear about where Incode stands.

On October 16, 2026, the Incode Platform was awarded FedRAMP In Process status, with the US General Services Administration (GSA) as our sponsoring agency. We’ve made FedRAMP authorization a priority over the past year. We are pursuing authorization at the Moderate impact level, with a target of Q1 2027.

That’s an exciting milestone, but it is not the finish line. In Process signals progress toward authorization, not an Authority to Operate (ATO). For readers still learning about the FedRAMP journey, here’s what that distinction means.

What FedRAMP In Process means

FedRAMP is the federal government's standardized program for assessing and authorizing cloud services. According to FedRAMP's own guidance, there are only three official designations: FedRAMP Ready, FedRAMP In Process, and FedRAMP Authorized. The program does not recognize any other label, including “FedRAMP compliant” or “FedRAMP equivalent.”

FedRAMP defines In Process as a designation for cloud services "that are actively working toward a FedRAMP authorization." In practice, it means a sponsoring agency has formally committed to working with the vendor toward authorization. The listing appears on the public FedRAMP Marketplace, where anyone can check it.

In Process status marks a commitment to the process. An Authority to Operate (ATO) and FedRAMP Authorized status come at the end of it, and only Authorized services are available for government-wide reuse.

I'd rather say that plainly than have anyone read more into it than is there.

Why FedRAMP Moderate matters for identity verification

FedRAMP categorizes cloud services into Low, Moderate, and High impact levels. Per FedRAMP, Moderate is the right fit when a loss of confidentiality, integrity, or availability "would result in serious adverse effects on a federal agency's operations, assets, or individuals." FedRAMP also notes that Moderate systems account for nearly 80% of the cloud services that receive FedRAMP authorization.

Identity verification touches some of the most sensitive data an agency handles: government IDs, biometrics, and the personal information people hand over to access benefits and services. Moderate is the bar that kind of data calls for.

How FedRAMP adds a new option for agencies in high-security environments

Incode is already available to agencies in high-security government environments. Our identity platform runs on-premises, in private clouds, and even in fully air-gapped environments. Those are some of the most demanding security environments in the world, and they leave little room for “good enough.”

FedRAMP adds the piece that was missing: a path for agencies to use the same identity platform as a cloud service.

That sets us apart from much of the market. Most identity verification (IDV) providers are SaaS-only. Agencies that need on-premises or disconnected deployments have to look elsewhere, while agencies that want a cloud service get a tool that was never built for classified environments. We've built for both.

Why does that matter to you? One platform means one accountability chain. When threats change—as they do almost monthly with AI-generated deepfakes—the fix ships once and reaches every deployment type. Agencies don't have to coordinate updates across a patchwork of vendors.

Questions to ask a cloud identity verification vendor about FedRAMP

Whether you work with us or not, here's the short list I'd use to check any vendor's federal claims:

  1. What is your exact FedRAMP designation today—Ready, In Process, or Authorized? “Compliant” is not an official designation.
  2. Can I verify it myself? Look for the vendor on the FedRAMP Marketplace; a missing listing means no confirmed designation.
  3. At what impact level—Low, Moderate, or High? Does that level match the data your program handles?
  4. Who is your sponsoring agency, and what's your target date? A real effort has both.
  5. What exactly is in scope? Authorization applies only to a defined cloud service offering, so a vendor's other products may fall outside it.
  6. What if my mission requires more than the FedRAMP baseline controls? A solution that can run on-premises, in a private cloud, or in an air-gapped environment gives you more options. That flexibility can provide a path to IL5, IL6, or even SCIF deployments, subject to the requirements and approvals for each environment.

If a vendor can't answer all six quickly, that tells you something.

What happens next in the FedRAMP authorization process

We are continuing the assessment work with GSA and our independent assessor, targeting authorization in Q1 2027. That timeline is a target, not a guarantee: authorization depends on the independent assessment and the sponsoring agency's decision.

In the meantime, agencies and partners can look up the listing on the FedRAMP Marketplace.

FedRAMP In Process status as public proof of progress

FedRAMP In Process status shows we are moving toward authorization, with a public listing you can verify.

Ready to see how Incode supports federal agencies across cloud, on-premise, and air-gapped deployments? Request a demo today.

Ready to see it in action?

Request a demo