Conceptual render: a library of modular silicon blocks, a few lifted and lit in copper.

Tested and proven. Now make it yours.

Once your bitfile has passed your tests in the Remote FPGA Lab, choose how to take it into your product: a production licence for the bitfile, the full source code of the project, or the ASIC path.

Discuss Licensing →Compare options

Conceptual illustration

01The path

Nothing to buy until it works.

Licensing is optional and comes last. You only decide once you've seen the design running on real hardware.

BuildDevice-locked bitfile

Generated by SIGPT from your prompt for the registered device.

TestRemote FPGA Lab

Test on a real AMD board, available 24/7 from $5/hr.

DecideLicence or source code

Optionally license the bitfile for FPGA production, or buy the full project source.

02Options

Three ways forward.

Every project starts with an evaluation bitfile for testing. When you're ready, choose the licence that fits how you'll ship.

01 · INCLUDED

Evaluation bitfile

For testing in the Remote FPGA Lab or on your registered board.

Device-locked bitfile for the registered device
Matching firmware image for RISC-V designs
Build, resource and timing reports where available
Use in Remote FPGA Lab sessions
Not licensed for production or commercial deployment
No source code

Test in the Remote Lab

Most chosen path 02 · OPTIONAL PURCHASE

Production licence

Ship the tested bitfile in your product, on your registered devices.

Commercial right to deploy the bitfile, and its generated firmware, in production
Device-locked to your registered production FPGAs
Licensing matched to your device count or volume
Rebuilds for new registered devices under the licence
Source code not included

Request a production licence →

03 · OPTIONAL PURCHASE

Full source code

Own the project: modify, re-target and maintain it with your own team.

Complete project source: integration logic, configuration and generated firmware source
Constraints, build scripts and project files
IP delivered in source or licensed form, per IP terms
Freedom to modify and re-target under the agreement
Engineering hand-over support

Enquire about source code

Exact terms, scope and pricing are agreed per project. Some third-party or partner IP may carry its own licence conditions, and these are set out before purchase.

03Compare

At a glance.

What you get	Evaluation	Production licence	Full source code
Device-locked bitfile	Included	Included	Included
Remote FPGA Lab testing	Yes	Yes	Yes
Commercial production use	No	Yes, registered devices	Yes, per agreement
Rebuilds for new devices	No	By SIGPT, under licence	By your team
Generated RISC-V firmware	Image for testing	Image, for production	Full C source
Project source files	No	No	Yes
Modify & re-target	No	Via SIGPT	Yes
Best for	Proving the design	Shipping quickly with SIGPT support	Long-term ownership and in-house maintenance

FAQLicensing

Common questions.

Do I have to buy anything after testing?

No. Both the production licence and source-code purchase are optional. You can stop after evaluation.

Can I upgrade from a production licence to source code later?

Yes. Talk to us and we'll scope a source-code purchase for the same project.

How is a production licence priced?

Pricing depends on the project, the IP involved and the number of devices or volume you plan to deploy. We agree it with you before purchase.

Is every IP available in source form?

Not always. Some IP may be delivered as licensed, encrypted or netlist blocks under its own terms. We set this out clearly before any source-code purchase.

Does a production licence mean production-ready?

A production licence grants the right to deploy the bitfile. Your own product qualification, certification and system testing remain your responsibility.

Proven on real hardware. Ready for your product.

Tell us how you plan to ship, and we'll propose the right licence.

Discuss Licensing →Remote FPGA Lab