×

Data Protection Policy

At LogikHaus, we take your privacy seriously. We are fully committed to protecting your personal information in compliance with Singapore's Personal Data Protection Act (PDPA) 2012.

How we handle your data:

For more information on your rights under Singapore Law, please visit:

→ Singapore Statutes Online (PDPA 2012) → DLA Piper Global Data Protection Guide (Singapore)

Guide

How to Choose an FPGA Design Services Company: A Practical Checklist

Outsourcing FPGA design can save months, or cost them. This checklist covers what to ask before you hire an FPGA design services company: relevant experience, toolchains, verification, deliverables and IP ownership.

When does it make sense to outsource FPGA design?

FPGA design is specialised work. The language, the tools and the verification methods are different from software, and experience counts for a lot. Outsourcing usually makes sense when:

  • You have no in-house FPGA team, or your team is fully booked and the schedule cannot move.
  • The design needs a specialism you lack, such as DSP and RF signal processing, high-speed serial links, motion control or cryptography.
  • Verification is the bottleneck. Many teams can write RTL but lack the time or experience to verify it properly before hardware.
  • You are prototyping an ASIC on an FPGA and need people who understand both sides.
  • You need a first working version quickly to prove a concept to customers or investors.

What FPGA design services usually cover

A full-service FPGA design company can take a project from requirements to working hardware, or pick up just one part of it. The typical stages are:

  1. Specification: measurable requirements for interfaces, data rates, latency, target device and power.
  2. Architecture: block structure, clock domains, pipelining and resource estimates.
  3. RTL design in VHDL or Verilog.
  4. Verification in simulation, with self-checking testbenches.
  5. Synthesis, place and route and timing closure in the FPGA vendor's toolchain.
  6. Bring-up on real hardware, against real interfaces and data.

Some companies also design the board, supply ready-made IP cores, or characterise high-speed links. For a step-by-step explanation of each stage, see our FPGA design guide.

The checklist: 10 questions to ask an FPGA design company

1. Have you built something like this before?

Ask for case studies in your application area, such as signal processing, video, motor control or communications. A company that has built a similar design knows where the difficult parts are. Even when customer names are confidential, a good company can describe the project, its scope and how long it took.

2. Which FPGA vendors and toolchains do you use?

Each FPGA vendor has its own tools: AMD Xilinx Vivado, Altera Quartus, Lattice Diamond, Gowin EDA and others. If you have already chosen a device, make sure the company is fluent in that toolchain. If you have not, a company that works across vendors can help you choose on cost, resources and availability rather than habit.

3. How do you verify the design?

This is the most important question, and the answer separates experienced teams from the rest. Look for self-checking testbenches, a test plan, and a structured method such as OSVVM for VHDL or UVM for SystemVerilog. Ask what is verified in simulation before anything reaches hardware. "We test it on the board" is not a verification strategy.

4. Do you work in our design language?

If your team will maintain the design after delivery, it should be written in the language they use, VHDL or Verilog. Mixed-language designs work, but they add friction for whoever maintains them. Our VHDL design guide covers what good, synthesisable VHDL looks like.

5. Who brings the design up on hardware, and with what equipment?

Bring-up and lab measurement can need oscilloscopes, logic analysers and high-speed test equipment. Agree up front whether testing happens at the design company, at your site, or on your equipment, and who is responsible for the target board.

6. What exactly will we receive?

Get the deliverables in writing. A complete delivery normally includes the RTL source, testbenches and test results, timing constraints, build scripts or project files, and documentation good enough for another engineer to pick the design up. Without the testbenches and constraints, you will struggle to change the design later.

7. Who owns the IP?

Agree ownership in the contract before work starts. Many design companies reuse their own proven IP cores to save you time and money. That is usually a good thing, but those cores are often licensed to you rather than transferred, so check the terms.

8. How do you handle confidentiality?

You will probably share specifications and product plans. Expect to sign an NDA before discussing details, and expect a professional company to protect its other customers' information in the same way, for example by describing past projects without naming customers.

9. How will we communicate and track progress?

Ask about milestones, progress reports and who your technical contact will be. If the company is in a different time zone, agree when you can reach each other. Regular demonstrations of working simulations or hardware are a better measure of progress than written reports.

10. How do you price the work?

Find out whether the quote is fixed price or time and materials, what it includes, and how changes to the specification are handled. The next section explains the trade-offs.

Fixed price or time and materials?

Fixed priceTime and materials
Best whenThe specification is clear and stableRequirements are still evolving, or the work is exploratory
Cost certaintyHigh, if the scope does not changeLower, but you only pay for work done
ChangesHandled through change requests, often at extra costEasy to absorb
What you need to provideA detailed, agreed specificationRegular reviews and clear priorities

A common middle ground is to start with a short, paid specification or architecture phase, then fix the price for the implementation once the scope is clear.

What to prepare before you ask for a quote

The more of this you can share, the more accurate and comparable your quotes will be:

  • What the design must do, and the interfaces it connects to.
  • Data rates, latency and throughput targets.
  • Target FPGA device or family, if already chosen, and the board it sits on.
  • Any existing RTL, IP cores or reference designs, and their language.
  • Expected production volume, and whether an ASIC could follow.
  • Your schedule, and the date a first working version is needed.
  • What you want delivered, and which parts your team will do.

About LogikHaus

LogikHaus is a fabless ASIC and FPGA design company:

  • Experience: 24+ years of FPGA and ASIC design. Past projects include a servo controller IP core for robotics, RF signal processing for a software-defined radio, FFT and DSP cores for a Singapore government agency, and a gyroscope and accelerometer data acquisition system for a marine vehicle.
  • Toolchains: Vivado, Quartus, Lattice Diamond, Gowin EDA and Synplify Pro. LogikHaus is a Gowin FPGA partner.
  • Verification: self-checking testbenches with OSVVM and UVM.
  • Languages: VHDL and Verilog.
  • Hardware: our own FPGA boards and SOM modules, and high-speed transceiver characterization carried out on the customer's lab equipment.
  • Customers: worldwide, including Japan, Korea, China and Europe.

FPGA design services

Architecture, RTL design, verification, timing closure and bring-up, plus IP cores and case studies.

See our FPGA design services

ASIC design and verification

Pre-silicon verification with testbenches and testcases, and digital, mixed-signal and RFIC ASIC design.

See our ASIC design services

Frequently asked questions

How much do FPGA design services cost?

It depends mainly on the size of the design, how much of it already exists, the verification depth required and whether board design and hardware bring-up are included. A clear specification is the best way to get an accurate quote, and to compare quotes from different companies fairly.

How long does an FPGA design project take?

Anything from a few weeks to many months. A basic first version of a focused block can be delivered within about a month, while a complete IP core designed from scratch can take the better part of a year. Ask for a milestone plan with a working first version early.

Should my FPGA design be written in VHDL or Verilog?

Both are fully supported by all major FPGA toolchains. The best choice is usually the language your team or existing codebase already uses, so you can maintain the design after delivery. Choose a design partner who works in that language.

Who owns the IP when I outsource FPGA design?

That is set by your contract, so agree it before work starts. Check who owns the new design, and whether any of the design company's own pre-existing IP cores are included under a licence rather than transferred to you.