GAL-2 Technologies

Home
United States
Newark, DE
GAL-2 Technologies

GAL-2 Time Contract for resilient digital infrastructure. Governed time before application state. gal-2.com

Application-facing temporal governance, holdover, rejoin, fail-closed behavior and IXOYE Witness Layer. GAL-2™ Technologies — Global Alignment Layer | Fractal Time. Eliminating drift & leap seconds for finance, IoT & telecom. Founded by Francisco Edgardo Torres Alvarado, visionary entrepreneur bringing the future of time.

10/27/2026

Your application can survive a network outage. But can it survive unsafe time?

What happens when your time source disappears?

Meet GAL-2 Time. Two ways to consume it.

🔹 Direct GAL-2 API
Access GAL-2 Time with an authenticated API key. No local installation required.

🔹 GAL-2 Node RC11
Local time consumption with bounded HOLDOVER, explicit uncertainty, controlled recovery, and fail-closed protection.

No need to replace your UTC, NTP, PTP, or GNSS infrastructure.

Keep your timing stack. Add GAL-2.

Start with the API. Evaluate the Node.

🌐 globalalignmentlayer.com/pricing

When time becomes unreliable, does your application know when to stop trusting it?

09/29/2026

GNSS can provide timing.
NTP can distribute it.
PTP can synchronize it.
UTC defines the reference timescale.

But there’s still another question:

Once time reaches the application, who decides whether it is safe to consume?

That’s the layer I’m exploring with GAL-2.

PTP TimeSynchronization ResilientTiming CriticalInfrastructure GAL2Technologies GAL2

09/12/2026

What happens when temporal trust becomes an authorization decision?

We tested GAL-2 Node RC11 in front of MIT Kerberos.

Kerberos did not need GAL-2 to replace its system clock or rewrite its internal time handling.

Instead, GAL-2 acted as an application-facing policy boundary before protected Kerberos operations.

When the GAL-2 Provider permitted consumption, the Kerberos flow proceeded.

When the Provider denied it, the protected flow did not start.

Results

• 500 paired AS-REQ measurements
• 500 paired TGS-REQ measurements
• 0 failed measurements
• 660 attempts during fail-closed testing
• 491 permits
• 169 denies
• 491 successful permitted Kerberos flows
• 0 Kerberos flows initiated after a GAL-2 deny

That distinction matters.

GAL-2 is not another clock.

It adds an explicit policy boundary between timing infrastructure and the application that ultimately decides whether time is safe to consume and act upon.

Keep your timing stack. Install the Node. Connect the application once.

Founder-operated PoC. Public methodology and evidence:
https://doi.org/10.5281/zenodo.22712811

Linux Infrastructure

09/11/2026

Time safety should not depend on the operating system.

GAL-2 Node RC11 brings the same application-facing time consumption governance model across macOS Apple Silicon, Linux ARM64 and Linux x86_64.

GAL-2 does not replace NTP, PTP, GNSS or the existing timing stack.

Instead, it adds an explicit policy boundary at the point where an application consumes time.

Through the GAL-2 Time Contract, the application can evaluate state such as safe_to_consume, operating mode, uncertainty, reason and source lineage before deciding whether time is acceptable under policy.

When that policy is no longer satisfied, consumption can be refused rather than silently continuing with unqualified time.

Keep your timing stack. Protect the consumer.

GAL-2 Node RC11
gal-2.com

TimeSynchronization

09/07/2026

Don’t trust GAL-2 Node. Test it. Break it.

The GAL-2 Node RC11 Linux AMD64 evaluator is now available for independent testing.

We want engineers to test the failure cases:

Disconnect the upstream. Let holdover age. Cross the policy boundary. Disturb the host clock. Restart the system. Restore connectivity.

Then ask one question:

Does the application still know whether time is safe to consume?

GAL-2 Node does not replace NTP or PTP. It adds an application-facing temporal governance boundary through the Time Contract.

RC11 has already completed founder-operated, real-duration 72-hour upstream-outage endurance runs on macOS Apple Silicon and Linux ARM64.

Now we want independent operators to test it themselves.

Evaluator release:
https://github.com/gal-2-technologies/gal2-node-rc11-amd64-evaluator/releases/tag/v1.0.0-rc11-amd64-evaluator

An evaluator API key is required. Temporary evaluator keys are available on request. DM us to get one.

If you run it, send us the failures too.

Keep your timing stack. Govern when your application should trust time.

Resilience CriticalInfrastructure

08/30/2026

72 hours. Two platforms. Both PASS.

GAL-2 Node RC11 completed real-duration upstream-outage endurance runs on macOS Apple Silicon and Linux ARM64.

LIVE → HOLDOVER → DEGRADED → FAIL_CLOSED → REJOIN → LIVE

No backward steps observed.

Public evidence:
DOI 10.5281/zenodo.22164457

Next step: independent reproduction.

DM for a temporary evaluator API key.

08/21/2026

The timing stack has a missing layer.

NTP, PTP, GNSS, atomic clocks and timing appliances are built to deliver time.

GAL-2 adds something different: application-facing time governance.

It governs whether an enrolled application should consume time before that time becomes trusted state.

We recently exercised GAL-2 under Telstra-class failure conditions involving upstream loss and recovery.

Today, the public RC11 macOS artifact is running a real-duration 72-hour continuous upstream outage test.

Your timing stack delivers time.
GAL-2 governs its consumption.

A new infrastructure category is emerging at the application boundary.

TimeGovernance

08/16/2026

Most systems try to make the clock better.

GAL-2 asks a different question:

Should the application trust time right now?

If the timing stack degrades, should the app keep going or know when to refuse?

08/15/2026

GAL-2 Node RC10 is now open for technical evaluation on Linux ARM64.

GAL-2 API creates GAL-2 Time.
GAL-2 Node makes it locally consumable.
The Time Contract governs its use.

What should an application do when time can no longer be safely consumed?

RC10 demonstrates bounded HOLDOVER, controlled recovery and REJOIN, FAIL_CLOSED behavior, and no silent fallback to raw host time.

Keep your timing stack.
Install the GAL-2 Node.
Connect the application once.

Technical evaluation and early pilot access are now open.

Need an evaluation API key? DM us or email [email protected].

08/12/2026

Something new is coming to the timing stack.

For years, applications have been expected to consume whatever time the system gives them. GAL-2 takes a different approach.

The GAL-2 API creates GAL-2 Time.
The GAL-2 Node makes it locally consumable.
The Time Contract governs its use.

The Node sits alongside your existing timing infrastructure. It does not replace NTP, PTP, or GNSS, and it does not discipline the host clock.

Keep your timing stack.
Install the GAL-2 Node.
Connect the application once.

Internal validation and endurance testing for the GAL-2 Node v1.0 release candidate are complete, including bounded holdover, controlled rejoin, fail-closed behavior, and application-level consumption without silent fallback to raw host time.

Technical evaluation access opens in September 2026 at gal-2.com.

GAL-2 is not another clock.

It’s a new application-level layer for deciding when time is safe to consume.

More soon.

Address

254 Chapman Road, Ste 208 #23982
Newark, DE
19702

Website

http://GAL-2.com/

Alerts

Be the first to know and let us send you an email when GAL-2 Technologies posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.