AISLER Push for Altium Designer

Layer Stackup

For your convenience we offer ready-to-use layer stackups for Altium.

Set up Push for Altium

Using Push for Altium we offer the most comfortable way to transmit projects from Altium Designer to us.

Copy you Organization Access Key

  • Open and click on “Account” in the upper-right corner of the page.
  • Click on “Settings” in the navigation menu on the left.
  • Copy the value below “Organization Access Key”. It should look like “f5c394b3db2f8d28ddf5”.

Add Publishing Destination

  • Open the “Preferences” dialog by clicking the preferences_btn button in the upper-right hand area of the design space.
  • Select “Data Managment” → “Publishing Destinations” from the menu on the left.
  • Using “Add Destination” add a new " Amazon S3" destination.
  • Fill out all input fields as shown in the screenshot.
    Name: Push to AISLER
    Account Name: AISLER
    Secret Access Key: y3jAQOlaGMXgvF0gx6PJNSqazxOP3bj2eeBirvwK
    Bucket: push-for-altium-v
    Key Prefix: Paste the “Organization Access Key” from your organization’s general settings as described in the first step.
    Last but not least, set the check mark at “Zip content”
  • Confirm the form. A new publishing destination should show up.

Import the output configuration

Using Right-click → “Save Link as…” download our Altium Outjob Configuration.
Using “Add Existing to Project…” on the “Projects Panel”, import the Outjob configuration to your project and assign the layout you would like to submit.

Push your project

On the right hand side of the Outjob form, click “Generate and Publish” and select “Push to AISLER…”.

After just a few seconds a prompt should open up. Enter either a new project name (“Awesome Project”) or copy an existing repository / project path (“sandbox/awesome_project”).

How to document component mount type

In order to provide accurate pricing for our Amazing Assembly offering it is necessary to document the mount type of all components used. To do so the component’s parameters in Altium are used. Our import application will look for a parameter called “Mounting Technology”. Please follow this guide on how to add this parameter.

Open Altium’s Parameter Manager while the project is open.

Screenshot 2021-08-27 134410

Only select “Parts”

Using the button “Add Column…” add a column called “Mounting Technology”.

Now it is time to poplate the recently added column / parameter.

On all parts / components used on your schematic, add either

  • “smt” or “surface mount”
  • “tht” or “through hole

depending on the technology used.

How to document component part numbers / manufacturer part numbers

In order to make use of our automatic part assignment on import it is required to use one of the following values on your BOM in Altium Designer

  • Part Number
  • PartNumber
  • Manufacturer_Part_Number_1
  • Comment

As soon as one of these includes a manufacturer part number (MPN) it will be automatically assigned on import. Our Output Configuration mentioned above already includes these columns, please make sure they are correctly filled.


I think there is a typo in your last lines, and maybe it would be more clear to write it like:

  • “smt” or “surface mount”
  • “tht” or “through hole”
    Just to make clear that there are four “variables” for two different mounting technologies.

Hi @RPhilbo thanks for the comment, indeed this makes things more clear. We’ve updated the tutorial accordingly.


I tried uploading a PCB made with Altium and their traditional Gerber Export (non X2) and NC Drill files. However, the Aisler tool does not find the NC-Drill files (.TXT). When using your Gerber X2 output job, everything works fine. According to your compatibility matrix traditional Gerber with Altium should work, any idea how to solve it?

(Motivation: At our company we generate ODB and RS-274-X gerbers for all designs and archive them, and it would be nice to order from them without having to genereate Data specifically for Aisler.)

Hi @Mobatime, welcome to the community.

Is there a reason you cannot use AISLER as a publishing destination. This would work out of the box and we ensure that all data is accurate. Please do not use the OutJob because this solution has been deprecated.

Hi @Felix-from-AISLER

Its a process thing. We generate and archive all gerber data, our purchase team does not have access to Altium to order PCBs. We give them the gerber, they order. I would like to use Aisler for prototypes, but id rather not establish a separate process just for Aisler. Id like to generate RS274-X gerber, zip it and upload to Aisler (BTW this is the default way in most small batch fabs). Any chance that’s possible?

Best regards, Chris from Mobatime

Hi Chris (@Mobatime)

I agree we are a little different here, but in the end your folks would be a lot faster that way. Here’s how this would work:
You invite your fellow purchasers to the account using our Teams-Function. That way, they will get access to your projects. You can then just send them an e-mail to the project with the specified quantity and they can place a purchase or even use the quoting process, if so required.

Just to understand you right, anything other than Aisler Push is deprecated? It is possible to upload a Zip archive with Gerbers (if they are named in some specific way), but you won’t support it in the future?

we do support Gerber, but it will not have the nitty-gritty-feature-set like Smart Tests. So at this moment I can only recommend you to use AISLER Push for Altium, as it provides the best experience.

Submitting Gerber is a possibility, but it has a lot of potential pitfals that you can circumvent by using AISLER Push for Altium.

I am having issues directly pushing to Aisler, I downloaded your preconfigured OutJob file, but somehow all of my holes and Vias don’t get pushed over. Do I have to manually configure a NC output as well?

Hi, this is a little late but maybe helps someone else. I had the same issue. Manually adding NC Drill Files to the Fabrication Outputs within the “push-to-aisler.Outjob” worked for me.

I would like to add, that the new parameter will only get pushed to aisler, if the .pcbdoc was updated from the .schdoc beforehand.

I am currently trying to order my first design from Aisler.

I have components in my design that i would like to see provided.
These parts are some mechanical and THT parts, no assembly is needed.
Just deploy ist to the shipment an thats it. Is that possible?

Will there be also a Design Rule file for 6 Layer PCBs for Kicad here @ aisler-support/design-rules/kicad at master · AislerHQ/aisler-support · GitHub

Good day, it’s possible add also a Design Rule stackup file for 4 Layer PCB for Altium in the following repo: aisler-support/push-for-altium at master · AislerHQ/aisler-support · GitHub

I ordered some boards back in october 2022 without any issues, but now I get a strange error message when trying to push to Aisler that the zip contains no files. It is using the exact same outjob as in october. Anyone knows what could be the cause?

Skärmbild 2023-01-23 011905

1 Like

Hi @Axeand ,

we added another output container to the OutJob, one for “basic ZIP output” and another for our “Push to AISLER”. Depending on which one you prefer you have to connect the output files to the container, just drag a line from the file to the container,


Hi - I just tried uploading a design following the above tutorial.

I can see the project in my account OK, but there are no drills/holes detected for the PCB. Typically we would generate an NC Drills set of files for this, but this appears to be missing from the outputjob?

This works fine for me so far with very small designs, but I have to create a new set of parameters and copy/paste the contents to match your parameter naming (as I can’t change my company database parameters just for a single manufacturer), even though the contents of the parameters are already what you need.

So here’s some suggestions for additional parameter names to look for, that I’ve seen commonly used across multiple organizations:
Mounting Technology: “Mounting”, “Mounting Type”
Part Number: “Manufacturer Part Number”, “MPN”

I have the same problem as Axeand and If I understand your answer correctly I have the correct files connected to the container as you can see in the screenshot.

Any idea what the probel might be. It worked a few weeks ago but at the moment I always get this error.

Best regards